Fix SM init crypto

[dani-garcia]

🎟️ Tracking

📔 Objective

Before the crypto refactor a user key was required to initialize crypto. Because secrets manager only has a single organization key, we used to set it as the user key and internally whenever an organization key was requested we'd return the user key if there was no private key.

With the crypto refactor, we removed this user key requirement and the code fallback when selecting a key, but we didn't change the initialization method to save the key as an organization key.

This PR changes the secrets manager initialization to do the correct thing here, and also brings a mocked test that was previously disabled in core to the bitwarden-sm crate. I've also fixed some compile time features that were incorrect and were causing compilation issues when running tests on bitwarden-sm.

⏰ Reminders before review

• Contributor guidelines followed
• All formatters and local linters executed and passed
• Written new unit and / or integration tests where applicable
• Protected functional changes with optionality (feature flags)
• Used internationalization (i18n) for all UI strings
• CI builds passed
• Communicated to DevOps any deployment requirements
• Updated any necessary documentation (Confluence, contributing docs) or informed the documentation
  team

🦮 Reviewer guidelines

• 👍 (:+1:) or similar for great changes
• 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
• ❓ (:question:) for questions
• 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed
  issue and could potentially benefit from discussion
• 🎨 (:art:) for suggestions / improvements
• ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
• 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
• ⛏ (:pick:) for minor or nitpick changes

[github-actions]

Checkmarx One – Scan Summary & Details – 6ace020b-7047-45f4-b577-8bd6f18d519d

Great job, no security vulnerabilities found in this Pull Request

[codecov]

Codecov Report

Attention: Patch coverage is 97.45763% with 3 lines in your changes missing coverage. Please review.

Project coverage is 68.87%. Comparing base (82f69c3) to head (a2ef268).
Report is 1 commits behind head on main.

Files with missing lines	Patch %	Lines
...ates/bitwarden-core/src/auth/login/access_token.rs	50.00%	3 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #260      +/-   ##
==========================================
+ Coverage   66.84%   68.87%   +2.03%     
==========================================
  Files         213      212       -1     
  Lines       15926    16025      +99     
==========================================
+ Hits        10645    11038     +393     
+ Misses       5281     4987     -294     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud