Allow multiple workspaces to share a single Azure DevOps integration

Description: As an admin managing separate, language-specific workspaces, I need both workspaces to connect to the same Azure DevOps account so work items and statuses stay synchronized without manual updates. Today, the product restricts an Azure DevOps integration to a single workspace, forcing duplicate configurations and manual status updates in one workspace. Purpose: Enable native, multi-workspace linking to a single Azure DevOps organization/account so teams can operate separate workspaces while relying on one centralized Azure DevOps environment. Benefits: Removes manual status updates and reduces operational overhead. Maintains a single source of truth in Azure DevOps. Avoids duplicated integrations and configuration drift across workspaces. Supports multilingual or multi-product setups that share the same Azure DevOps org. Key Features: Allow one Azure DevOps connection to be referenced by multiple workspaces within the product. Per-workspace mappings for Azure DevOps projects, work item types, and status fields using the shared connection. Reliable event handling so updates from Azure DevOps are routed only to the correctly mapped workspace(s) without duplication. Clear admin UI to select and reuse an existing Azure DevOps connection when configuring additional workspaces. Access control and audit visibility showing which workspaces are linked to the shared connection. Backward compatibility so existing single-workspace integrations continue working without changes.