Platform/pm 2535/upgrade to azure messaging servicebus

[MGibson1]

Type of change

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

Objective

Dependency update of Microsoft.Azure.ServiceBus to Azure.Messaging.ServiceBus.

Code changes

• launch.json: We build service bus subjects based on the value of an environment variable and the service that is running.
• packages.lock.json/core.csproj: Remove Microsoft.Azure.ServiceBus and add Azure.Messaging.ServiceBus
• applicationCacheHostedService / InMemoryServiceBusApplicationCache: Use the new ServiceBusClient and ServiceBusAdministrativeClient to coordinate reading/writing messages

Before you submit

• Please check for formatting errors (dotnet format --verify-no-changes) (required)
• If making database changes - make sure you also update Entity Framework queries and/or migrations
• Please add unit tests where it makes sense to do so (encouraged but not required)
• If this change requires a documentation update - notify the documentation team
• If this change has particular deployment requirements - notify the DevOps team

[bitwarden-bot]

Checkmarx One – Scan Summary & Details – 3534bcd3-3474-4c3f-83f7-d8f56fef4b16

No New Or Fixed Issues Found

[withinfocus]

I have been interested in seeing this change so this is great! Couple questions.

[withinfocus]

❓ Is it safe to call CreateSender in the constructor?

[MGibson1]

Yes, that's the recommended practice: https://learn.microsoft.com/en-us/azure/service-bus-messaging/service-bus-performance-improvements?tabs=net-standard-sdk-2#reusing-factories-and-clients

[withinfocus]

Only lock file updates. This is gonna help a ton of PRs though!