Consider supporting subscription IDs in existing resource scope

### Is there an existing issue for this?

- [x] I have searched the existing issues

### Is your feature request related to a problem? Please describe the problem.

The existing resource support that we added in 9.1 allows referencing existing resources that have been provisioned in the same or a different resource group. Although it is possible to reference existing resources in Bicep in different subscriptions, we don't support this.

### Describe the solution you'd like

Expose overloads and additional APIs that allow setting the subscription ID on an existing resource. This would consist of:

- Updates to the `ExistingAzureResourceAnnotation` to reference different subscription IDs
- Update to the manifest schema to encode the subscription ID referenced for consumption by deployment tools
- Updates to the local Bicep provisioner to support referencing resources in different subscriptions
- Updates to the existing extension methods and configure infrastructure calls to encode the subscription ID

### Additional context

_No response_