f439a6cd9e
### Summary This PR fixes an inconsistency in the display of application versions in the Admin Panel. Previously, the "Current version" was displayed with a "v" prefix (e.g., `v1.1.1`), while the "Latest version" was displayed without it (e.g., `1.1.1`). ### Problem The inconsistency originated from two different data sources being handled differently in the backend: - `currentVersion` was read directly from the `APP_VERSION` configuration variable, which includes the "v" prefix. - `latestVersion` was fetched from the Docker Hub API, and the `semver.coerce()` function was used to parse it, which strips the "v" prefix.  ### Solution The fix addresses the root cause in the [AdminPanelService] on the backend. The `semver.coerce()` function is now also applied to the `currentVersion`. This ensures that both version numbers are normalized at the data source, providing a consistent format before being sent to the frontend. This is a cleaner approach than manipulating the data on the client side. **Before:** - Current version: `v1.1.1` - Latest version: `1.1.1` **After:** - Current version: `1.1.1` - Latest version: `1.1.1` --------- Co-authored-by: prastoin <paul@twenty.com>