fix: versionBadge usage after update

Signed-off-by: Piotr Zaniewski <[email protected]>

platform/administer/connector/database.mdx

@@ -11,7 +11,7 @@ import InstallNextSteps from '../../_partials/install/install-next-steps.mdx';
 
 import VersionBadge from '@site/src/components/VersionBadge';
 
-<VersionBadge version="v4.1.0" vclusterVersion="v0.21.0"/>
+<VersionBadge platformVersion="v4.1.0" vclusterVersion="v0.21.0"/>
 
 The database connector feature allows an admin to configure a database server to manage backing stores for multiple virtual clusters. For each virtual cluster, the feature automatically creates an independent database and non-privileged user. Read more about the use of external databases in the [External Database documentation](/docs/vcluster/configure/vcluster-yaml/control-plane/components/backing-store/database/external).
 

platform/configure/cost-control.mdx

@@ -9,7 +9,7 @@ import VersionBadge from '@site/src/components/VersionBadge';
 
 The platform comes with the cost control dashboard enabled by default, offering insights into potential [cost savings](https://www.vcluster.com/cost-savings) through virtual clusters.
 
-<VersionBadge version="v4.2.0" vclusterVersion="v0.22.0"/>
+<VersionBadge platformVersion="v4.2.0" vclusterVersion="v0.22.0"/>
 
 To track allocations and calculate savings for workloads running inside
 virtual clusters the platform deploys and manages [Prometheus](https://prometheus.io/) and