chore: upgrade api7 and gateway to v3.10.3

[jarvis9443]

Version-bump-only release for API7 EE 3.10.3 (latest line → main).

Changes

• charts/api7: chart 3.10.1 → 3.10.2, appVersion 3.10.2 → 3.10.3; dashboard / dp_manager / developer_portal / file_server image tags v3.10.2 → v3.10.3.
• charts/gateway: chart 3.10.6 → 3.10.7, appVersion 3.10.2 → 3.10.3; gateway image tag 3.10.2 → 3.10.3.
• Regenerated README.md via make helm-docs.

No structural changes needed

• The raised shared-memory (lua_shared_dict) defaults for 3.10.3 (prometheus-metrics 128m, service-discovery 64m, tracing_buffer 32m, api-calls-for-portal 64m) are already present in charts/gateway/values.yaml from the earlier shared-dict PRs (feat(gateway): raise prometheus-metrics and tracing_buffer shared-dict defaults #310, fix(gateway): reduce prometheus shared dict to 128m #312).
• trusted_addresses is already templated in the gateway configmap; the new match_uri_encoded_slash global option can be set through apisix.customizedConfig, so no new value is required.
• No Control Plane chart (control-plane/helm) template or values changes between v3.10.2 and v3.10.3.

[coderabbitai]

Warning

Review limit reached

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

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 55 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 623aac90-6f46-44ed-b865-e5d8655df1bf

📥 Commits

Reviewing files that changed from the base of the PR and between b3cb5d8 and a5bd257.

📒 Files selected for processing (6)

• charts/api7/Chart.yaml
• charts/api7/README.md
• charts/api7/values.yaml
• charts/gateway/Chart.yaml
• charts/gateway/README.md
• charts/gateway/values.yaml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/upgrade-3.10.3

---

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