fix(connection-form): remove dependency on Node.js crypto module

[addaleax]

We can safely use the webcrypto API exposed through the crypto global in both Node.js and Electron now.

This enables removing a polyfill with a known vulnerability in the VSCode extension.

Description

Checklist

• New tests and/or benchmarks are included
• Documentation is changed or added
• If this change updates the UI, screenshots/videos are added and a design review is requested
• If this change could impact the load on the MongoDB cluster, please describe the expected and worst case impact
• I have signed the MongoDB Contributor License Agreement (https://www.mongodb.com/legal/contributor-agreement)

Motivation and Context

• Bugfix
• New feature
• Dependency update
• Misc

Open Questions

Dependents

Types of changes

• Backport Needed
• Patch (non-breaking change which fixes an issue)
• Minor (non-breaking change which adds functionality)
• Major (fix or feature that would cause existing functionality to change)

[Copilot]

Pull request overview

This PR removes the dependency on Node.js's crypto module by replacing it with the globally available crypto (Web Crypto API), which works in both Node.js and Electron environments. This change eliminates a polyfill with a known security vulnerability in the VSCode extension.

Key changes:

• Replaced Node.js crypto.randomBytes() with Web Crypto API's crypto.getRandomValues()
• Removed the import statement for Node.js crypto module