developer-portal-fe chart pins portal frontend v0.14.0, behind the shipped product

The developer-portal-fe chart still deploys api7/api7-ee-developer-portal-fe:v0.14.0 (appVersion: "0.14.0"), while API7 EE 3.10.6 and 3.10.7 both ship a newer Developer Portal frontend. Anyone deploying the portal frontend with this chart is therefore running a version that predates changes the release notes describe as shipped: 3.10.6 announced the portal frontend rebuilt on TanStack Start, and 3.10.7 fixes the OpenAPI document download filename for external API products and pasting into the interactive API documentation viewer (including the Basic Auth credential fields). None of that is reachable through this chart today.

I deliberately kept this out of the 3.10.7 release PR (#380). The jump from 0.14.0 to the current line crosses the framework rewrite, so the container contract is not the same as 0.14.0's — base image, entrypoint and shell availability all need re-checking. That deserves its own validation rather than riding along with a release version bump.

What it likely needs:

• confirm the container contract between 0.14.0 and the current portal FE release (entrypoint, base image, whether a shell is still present for anything that execs in)
• check whether the portal FE config schema gained keys worth surfacing in the chart's pass-through block
• bump appVersion and the image tag, with the chart version bumped accordingly

Worth noting this is not new in 3.10.7 — the chart was already behind at 3.10.6, so it has been silently diverging for at least two releases.

Start with the developer-portal-fe chart and compare its current image tag, appVersion, and pass-through configuration with the newer portal frontend shipped in API7 EE 3.10.6 and 3.10.7. Validate the container entrypoint, base image, shell availability, and configuration schema before updating the chart and its version. Done means the chart deploys the current frontend and exposes any required configuration without breaking existing container interactions.