Describe the bug

On on-premise instances, the version badge rendered in the top-right of the NavBar shows a duplicated leading v, e.g. vv0.159.15 instead of v0.159.15.

To Reproduce

Steps to reproduce the behavior:

1. Deploy any recent on-prem Infisical release (reproduced on v0.159.15, but the code path has existed since the VersionBadge component was introduced).
2. Log in and look at the NavBar in the top-right corner on a viewport ≥ md.
3. Observe the badge — it reads vv0.159.15.

Expected behavior

The badge should display v0.159.15 (a single leading v).

Screenshots

Rendered HTML (captured from an on-prem v0.159.15 instance):

<span data-slot="badge" class="... mt-[3px] mr-2 hidden md:inline-flex">vv0.159.15</span>

Root cause

• Release tags are named v0.159.15 (see https://github.com/Infisical/infisical/releases).
• The release workflow passes the tag name directly to the INFISICAL_PLATFORM_VERSION build arg:
  https://github.com/Infisical/infisical/blob/main/.github/workflows/release-standalone-docker-img-postgres-offical.yml

  - name: Extract version from tag
    id: extract_version
    run: echo "::set-output name=version::${GITHUB_REF_NAME}"
  ...
  INFISICAL_PLATFORM_VERSION=${{ steps.extract_version.outputs.version }}

  So INFISICAL_PLATFORM_VERSION (and therefore VITE_INFISICAL_PLATFORM_VERSION) is set to v0.159.15, already starting with a v.
• The frontend component then prepends another v:
  https://github.com/Infisical/infisical/blob/main/frontend/src/layouts/OrganizationLayout/components/NavBar/VersionBadge.tsx

  <Badge variant="neutral" className="mt-[3px] mr-2 hidden md:inline-flex">
    {`v${version}`}
  </Badge>

The backend already normalizes this by using v${INFISICAL_PLATFORM_VERSION} with a raw semver, so the issue is isolated to the frontend badge.

Proposed fix

Strip a leading v from version before re-prepending it, so the component is idempotent regardless of whether the env var is provided with or without the leading v (and matches the backend's logging format).

I've opened a PR with this fix:

Platform you are having the issue on

• On-premise / self-hosted, Docker infisical/infisical:v0.159.15

Additional context

• Only affects on-prem (cloud and dedicated instances skip rendering this badge).
• Visible on viewports md and up where the badge is inline-flex.