feat(web): show server versions on remote connections - #7271

💭 I need to check the actual implementation in ConnectionsSettings.tsx at that line to see how the label gets rendered. I'm wondering if there's a consistency issue with how the version is being displayed—whether other parts of the codebase format versions differently, like with a "v" prefix, or if the serverVersion metadata might be redundant with existing version tooltips. Let me look for version formatting helpers and check how versions are displayed elsewhere in the code. I'm noticing a potential bug where the new version helper unconditionally adds a "v" prefix, which could create "vv0.0.33" if serverVersion already starts with "v". I should check how normalizeVersion works in versionSkew.ts and trace where serverVersion originates to see if this double-prefixing is actually possible. The serverVersion from the config is likely just the bare version string without a "v" prefix, so a double-v is unlikely, and an empty string would only render as "v" which is a minor issue. I'm noticing a potential UI consistency problem though — the version mismatch tooltip elsewhere displays the version without the "v" prefix, but the metadata uses "v0.0.33", so there's some inconsistency in how versions are formatted across the interface. Looking at the styling and structure, this change fits within the existing metadata paragraph styling, so there's no new styling concerns. The "Server update available" tooltip already exposes the version comparison, so this isn't duplicating functionality. When disconnected, the server config might be stale, but that's handled with the "Last seen v..." messaging. There's a minor edge case where an empty or whitespace serverVersion could slip through since the helper only checks for null, not empty strings — the repo has a normalizeVersion function for this, but it's not a concrete violation by the ruleset. I'm leaning toward this being all clear.