ci: drop the unused apisix helm repo from CI and release

[jarvis9443]

The release run on #351 failed at the "Add Helm repo" step:

Error: looks like "https://charts.apiseven.com" is not a valid chart repository
or cannot be reached: Get "https://charts.apiseven.com/index.yaml": context
deadline exceeded (Client.Timeout exceeded while awaiting headers)

Nothing in this repo uses that repository. Every dependencies: entry in every
Chart.yaml and every Chart.lock resolves to charts.bitnami.com or
jaegertracing.github.io — the apisix repo has no consumer, in helm dependency
resolution or anywhere else. It was added in five places (four in ci.yaml, one in
release.yaml) and each one is a hard failure point, because helm repo add fetches
index.yaml before it will accept the URL.

It is also an alias rather than a real repo: https://charts.apiseven.com is a 301
to https://apache.github.io/apisix-helm-chart/, served from an IP the runners reach
unreliably. So every CI and release run has been paying a network round trip to a
host it does not need, with an outage of that host able to fail a release outright —
which is what happened on #351.

Removes all five occurrences. Verified that the remaining shell chains are still
valid (sh -n over every run: block) and that both workflow files still parse.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your current included review allowance is based on your included PR review attempts over the past 7 days.

Next review available in: 32 minutes

Limit details: You’ve used the included review currently available. Your 60 included PR review attempts over the past 7 days set your current allowance at 1 review per hour.

You’re in a promotional period — use the checkbox below to run this review for free:

• Run review for free

_{On-demand reviews are free for the next 31 days. After that, they cost $0.25 per reviewed file.}

How can I continue?

Run this review now using the option above, or comment @coderabbitai review --use-credits.

You can also wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 19d8d1c2-39a6-4559-a540-7ed9ea369bfa

📥 Commits

Reviewing files that changed from the base of the PR and between d53d685 and a6bd5d8.

📒 Files selected for processing (2)

• .github/workflows/ci.yaml
• .github/workflows/release.yaml

---

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.