Check both tenant and subscription before using shared Search resource

[alzimmermsft]

Description

Check both tenant and subscription before attempting to use shared resources.

All SDK Contribution checklist:

• The pull request does not introduce [breaking changes]
• CHANGELOG is updated for new features, bug fixes or other significant changes.
• I have read the contribution guidelines.

General Guidelines and Best Practices

• Title of the pull request is clear and informative.
• There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

• Pull request includes test coverage for the included changes.

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[Copilot]

Pull Request Overview

This PR refines the conditional logic for accessing static test resources in the Azure Search Bicep template. The change ensures that static resources are only used when both the tenant ID and subscription ID match specific values, providing more precise control over resource selection.

Key Changes

• Renamed variable from isTmeTenant to canUseStatic for clarity
• Enhanced condition to check both tenant ID and subscription ID (previously only checked tenant ID)
• Updated all references throughout the template to use the new variable name and logic

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).

[alzimmermsft]

/azp run java - search - tests

[azure-pipelines]

Azure Pipelines successfully started running 1 pipeline(s).