[PM-13377] Rename repository

[Hinton]

🎟️ Tracking

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

📔 Objective

Rename repository from sdk to sdk-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 – 4dfe4543-8597-4b35-a2a1-b4b4085c0750

New Issues

Severity	Issue	Source File / Package	Checkmarx Insight
	Apt Get Install Pin Version Not Defined	/Dockerfile: 9	When installing a package, its pin version should be defined
	Missing_HSTS_Header	/languages/php/example.php: 3	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/BitwardenClient.java: 43	Attack Vector
	Privacy_Violation	/languages/java/example/Example.java: 46	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/BitwardenClient.java: 43	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/BitwardenClient.java: 43	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/BitwardenClient.java: 43	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/BitwardenClient.java: 43	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/SecretsClient.java: 41	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/SecretsClient.java: 41	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/SecretsClient.java: 138	Attack Vector
	Privacy_Violation	/languages/java/example/Example.java: 43	Attack Vector
	Privacy_Violation	/languages/java/example/Example.java: 53	Attack Vector
	Privacy_Violation	/languages/java/src/main/java/com/bitwarden/sdk/SecretsClient.java: 20	Attack Vector
	Healthcheck Instruction Missing	/Dockerfile: 33	Ensure that HEALTHCHECK is being used. The HEALTHCHECK instruction tells Docker how to test a container to check that it is still working
	Missing_CSP_Header	/about.hbs: 48	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 129	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 122	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 115	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 151	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 129	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 115	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 151	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 129	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/Secrets.cpp: 56	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 151	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 129	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/Secrets.cpp: 139	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 122	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 115	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 151	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 129	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/Secrets.cpp: 107	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 159	Attack Vector
	Privacy_Violation	/languages/cpp/src/BitwardenClient.cpp: 136	Attack Vector
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 85	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-bws.yml: 51	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-napi.yml: 44	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-ruby.yml: 24	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/version-bump.yml: 53	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 172	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-go.yml: 89	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-ruby.yml: 51	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-java.yml: 82	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-bws.yml: 162	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 130	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-wasm.yml: 42	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-cpp.yml: 65	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-go.yml: 69	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-php.yml: 89	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-cpp.yml: 59	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-php.yml: 176	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-cli.yml: 337	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 60	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-napi.yml: 110	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-rust-crates.yml: 76	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-bws.yml: 92	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/build-cli-docker.yml: 53	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-dotnet.yml: 88	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-java.yml: 98	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-wasm.yml: 86	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-bws.yml: 168	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-bws.yml: 43	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/release-dotnet.yml: 54	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-python.yml: 107	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...
	Unpinned Actions Full Length Commit SHA	/publish-ruby.yml: 92	Pinning an action to a full length commit SHA is currently the only way to use an action as an immutable release. Pinning to a particular SHA helps...