feat(api7): support extraEnvVars for file server

[jarvis9443]

Fixes #332

file_server was the only deployment in the api7ee3 chart with no way to inject environment variables — dashboard, dp_manager, developer_portal and api_usage all expose extraEnvVars.

Adds file_server.extraEnvVars (default []) and renders it in file-server-deploy.yaml. The list goes through api7ee3.tplvalues.render, so entries may contain templates and valueFrom references, matching the other components. The whole env: block is guarded by the if, so the rendered Deployment is byte-identical to before when the value is left empty.

file_server:
  enabled: true
  extraEnvVars:
    - name: API7_LOG_LEVEL
      value: debug
    - name: RELEASE_NS
      value: "{{ .Release.Namespace }}"
    - name: FROM_SECRET
      valueFrom:
        secretKeyRef:
          name: my-secret
          key: token

Chart version 3.10.3 -> 3.10.4, README regenerated with helm-docs.

A parallel PR targets release/3.9 for the 3.9 line.

[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: 17 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: 8c0f4c78-f258-41fe-9cd9-743d3ff56849

📥 Commits

Reviewing files that changed from the base of the PR and between 0c7d74d and b3e0a97.

📒 Files selected for processing (4)

• charts/api7/Chart.yaml
• charts/api7/README.md
• charts/api7/templates/file-server-deploy.yaml
• charts/api7/values.yaml

---

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