fix: add missing property

src/docs/guides/bug-report.mdx

@@ -20,6 +20,7 @@ Here is an overview of each field in the bug report object sent:
 ```ts
 {
     userId: string, // A unique identifier for the user submitting the report. This helps in tracking bugs specific to user accounts or in following up with the user if needed.
+    sdkVersion: string, // The version of the SDK.
     title: string, // [User generated] A brief, descriptive title of the bug. This should be concise yet informative enough to give an overview of the issue.
     description: string, // [User generated] A detailed description of the bug. It should include what the user expected to happen and what actually happened. This field can contain error messages, observations, and any relevant details about the bug's behavior.
     steps: string, // [User generated] A step-by-step guide on how to reproduce the bug. This is crucial for developers to understand and fix the issue. Clear and precise steps can significantly speed up the debugging process.

src/docs/guides/metrics.mdx

@@ -34,7 +34,7 @@ For each request sent to the wallet, we record and send two key pieces of data t
     os: string, // The operating system of the user's device.
     walletName: string, // The name of the wallet being used.
     walletType: string, // The type of wallet being interacted with, categorized as "extension", "mobile", "web", or "desktop".
-    sdkVersion: string, // The version of the SDK being used for the wallet interaction.
+    sdkVersion: string, // The version of the SDK.
     transport: string, // The method used for connecting to the wallet. Options include "extension", "p2p" (peer-to-peer), "walletconnect", or "website".
     time: Date, // The timestamp when the request was made.
     action: string, // The type of action being performed, such as "connect", "message", or "disconnect".