Use-sdk-for-encrypt-decrypt

[MGibson1]

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-15093

📔 Objective

Introduces a namespace for pure SDK functions. This PR is a draft to invite discussion over a good way to handle SDK interfaces with differing levels of state.

Currently, SDKs are bound to a server only or a server and a specific authenticated user on that server. However, no type differences between these level of context exist. This PR introduces a new context, one without any state, so I called it BitwardenPure.

⏰ 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 – 6b27106a-292b-4cb0-bd72-f97ef8939bb5

Great job, no security vulnerabilities found in this Pull Request

[MGibson1]

@dani-garcia would you mind taking a look at this when you have a chance?