Allow attaching a cosmos db account with tenantId.

[mkrueger]

This pull request adds support for handling Azure Cosmos DB connection strings that use either an AccountKey or a TenantId for authentication, instead of requiring only an AccountKey. The changes update validation, parsing, and storage logic throughout the codebase to recognize and propagate TenantId values, and they add tests to ensure correct parsing. Additionally, the URI handler and workspace model are updated to support the new field.

Cosmos DB connection string handling:

• Updated validation and user prompts to accept connection strings that include AccountEndpoint and either AccountKey or TenantId, and clarified error messages and placeholders accordingly. [1] [2] [3]
• Extended the parseCosmosDBConnectionString function and ParsedCosmosDBConnectionString class to extract and store the TenantId property if present. [1] [2] [3]
• Added tests to ensure correct parsing of connection strings with TenantId and with only AccountEndpoint. [1] [2]

Workspace and storage model updates:

• Modified the CosmosDBAttachedAccountModel and related logic to include an optional tenantId field, and ensured the field is persisted and propagated where appropriate (e.g., in storage items and account info). [1] [2] [3] [4] [5]

URI handler and parameter propagation:

• Updated the URI handler to extract, mask, and propagate the tenantId parameter from URIs, and to store it in attached account storage items if present. [1] [2] [3] [4] [5] [6] [7] [8] [9]Fixes Allow attaching a Cosmos DB Account with tenantId (without AccountKey) #2620

[sevoku]

LGTM, tried with using a connection string with a specific tenant Id that is not my default and it works like a charm.