feat(azure): add AZUREVIRTUALNETWORKS candidate relationship for cros…

[nr-siranjeevi]

Adds a candidate relationship definition so the Entity Platform can resolve
Azure VNet targets across subscriptions and across NR accounts natively,
using the tag azure.resourceId that AZUREVIRTUALNETWORKS entities already
carry.

Related JIRA tickets:

• NR-582475 — Cross Subscription must work across NR Accounts
• NR-584562 — Block relationships to un-integrated subscriptions

Files:

• relationships/candidates/AZUREVIRTUALNETWORKS.yml — Lookup on the azure.resourceId tag. onMiss: CREATE_UNINSTRUMENTED produces an UNINSTRUMENTED-AZUREVIRTUALNETWORKS placeholder when the target subscription is not yet integrated / scanned; the platform auto-swaps to the real INFRA-AZUREVIRTUALNETWORKS entity when it later appears.
• entity-types/uninstrumented-azurevirtualnetworks/definition.yml — Required by the CREATE_UNINSTRUMENTED action. Owned by CMP.

Producer: azure-configuration-fetcher will emit CandidateRelationship messages against this category behind a per-NR-account feature flag that defaults to off. Skip-behavior side (which fixes the wrong-account registration bug from NR-584562) is already deployed to staging under azure-configuration-fetcher PR #42.

Api Review Board (ARB)

Not required — the ARB:not-required label has been applied to this PR. The change is additive (net-new candidate + net-new uninstrumented entity type owned by CMP), with no modifications to existing production entity types.

Checklist

• I've read the guidelines and understand the acceptance criteria.
• The value of the attribute marked as identifier will be unique and valid.
• I've confirmed that my entity type wasn't already defined.
• ARB approval is not required for this change (see label).

[CLAassistant]

All committers have signed the CLA.

[entityBot]

We don't think these changes require an API Review Board (ARB) review, so it is not required to merge this PR. Note that all API changes do require one: if you believe this PR needs an ARB review, please create the ticket and add the ARB:pending label. Reach #api-review-board in case of doubts.

[entityBot]

We don't think these changes require an API Review Board (ARB) review, so it is not required to merge this PR. Note that all API changes do require one: if you believe this PR needs an ARB review, please create the ticket and add the ARB:pending label. Reach #api-review-board in case of doubts.

Dismissing reviews

[entityBot]

We don't think these changes require an API Review Board (ARB) review, so it is not required to merge this PR. Note that all API changes do require one: if you believe this PR needs an ARB review, please create the ticket and add the ARB:pending label. Reach #api-review-board in case of doubts.

[nr-siranjeevi]

Hi — could someone from the EP team take another look at this PR? Context:

• Adds a new AZUREVIRTUALNETWORKS candidate relationship + uninstrumented entity type (no changes to existing production types).
• ARB is not required for this change — the ARB:not-required label is already applied.
• Producer side is already deployed to staging under azure-configuration-fetcher PR Update golden metrics #42, feature flag defaulted off.

Could you:

1. Re-add the EP:ready label (it was auto-removed when I pushed my last update).
2. Approve the pending Actions workflow runs — FOSSA CLI Analysis and Validation are stuck at "Waiting for workflow to run" because this is a fork PR from an external-contributor account.

Thanks.