chore: update sdk internal to 3.0.0 (#1515)

## 🎟️ Tracking

<!-- Paste the link to the Jira or GitHub issue or otherwise describe /
point to where this change is coming from. -->

## 📔 Objective

Update to sdk-internal 3.0.0 in preparation for sdk-sm release.

chore: update sdk internal to 3.0.0 (#1515)

## 🎟️ Tracking

<!-- Paste the link to the Jira or GitHub issue or otherwise describe /
point to where this change is coming from. -->

## 📔 Objective

Update to sdk-internal 3.0.0 in preparation for sdk-sm release.

chore: update sdk internal to 3.0.0 (#1515)

## 🎟️ Tracking

<!-- Paste the link to the Jira or GitHub issue or otherwise describe /
point to where this change is coming from. -->

## 📔 Objective

Update to sdk-internal 3.0.0 in preparation for sdk-sm release.

Bump bitwarden version to 2.0.0 (#1429)

## Type of change
    - [ ] Bug fix
    - [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
    - [ ] Build/deploy pipeline (DevOps)
    - [X] Other

    ## Objective
    Automated bitwarden version bump to 2.0.0

Releasing stuff

Merge remote-tracking branch 'origin/main' into debug-bws-cli

Bump dotnet-sdk version to 1.0.0 (#1208)

## Type of change
    - [ ] Bug fix
    - [ ] New feature development
- [ ] Tech debt (refactoring, code cleanup, dependency upgrades, etc)
    - [ ] Build/deploy pipeline (DevOps)
    - [X] Other

    ## Objective
    Automated dotnet-sdk version bump to 1.0.0

Release Python Workflow - Fix logic (#1102)

Fix moving schemas artifact to proper folder

[PM-12431] Temporarily un-export bitwarden_fido (#1072)

## 🎟️ Tracking

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

## 📔 Objective

Temporarily un-export `bitwarden-fido`. We can't release crates for
`1.0` because:
- `bitwarden-fido` currently relies on dependencies that are GitHub
repositories
([reference](https://doc.rust-lang.org/cargo/reference/specifying-dependencies.html#specifying-dependencies-from-other-registries))
- `bitwarden-fido` is not yet released (same with the aforementioned
dependencies)

This PR also includes the auto-updates to the `Cargo.lock file`, which
should be fine.

⭐️**NOTE**⭐️: This will break CI, this should only be merged when we are
ready to do 1.0 releases of `bitwarden`, `bws`, etc. It should quickly
be followed up a PR, after release, which reverses this.

## ⏰ 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

<!-- Suggested interactions but feel free to use (or not) as you desire!
-->

- 👍 (`:+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