[PM-13984] Added Futurex to list of supported PKCS #11 providers

[bbarrows-futurex]

Futurex and Bitwarden worked together to get the PKCS #11 integration working with the Futurex CryptoHub, and the documentation for it is published here:
https://docs.futurex.com/cryptohub-integration-guides/bitwarden

I don't know that code changes are required in this repository, but it would be great if Futurex could be included in any lists of supported HSMs for the integration.

[CLAassistant]

All committers have signed the CLA.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-13984

[bitwarden-bot]

Thank you for your contribution! We've added this to our internal Community PR board for review.
ID: PM-5517

[djsmith85]

@bbarrows-futurex Apologies for the delay here. Could you please provide a description to your PR. This will help Product management to review and if approved passed on to Engineering.

Kind regards,
Daniel

[pixman20]

Review Summary

PR: [PM-13984] Added Futurex to list of supported PKCS #11 providers

Aspect	Assessment
Risk	Low
Type	Feature addition
Security	No concerns
Testing	Adequate - test cases added for both Decrypt and Sign paths

Overview

Clean, well-structured community contribution that adds Futurex CryptoHub as a supported PKCS#11 HSM provider. All changes follow existing patterns exactly:

• README.md - Updated provider comment to include futurex
• KeyConnectorSettings.cs - Added futurex to the provider comment list
• Pkcs11RsaKeyService.cs - Added library path mapping in the LoadLibrary switch expression
• Pkcs11RsaKeyServiceTests.cs - Added InlineData test cases for both DecryptAsync and SignAsync library path resolution

No issues found. The change is purely additive, follows established conventions, and includes appropriate test coverage.