Inconsistent behavior when deleting secret referenced by Azure Queue scale rule (Single vs Multiple revision mode)

[v-ruizh]

OS: Win 11 x64
Build Version: 20260609.1

Repro Steps:

1. Create a Container App with an Azure Queue scale rule referencing a secret
2. Switch between Single and Multiple revision modes
3. Delete the referenced secret

Expect:
Deleting a referenced secret should be handled consistently, either by blocking deletion or by clearly indicating and validating broken dependencies.

Actual:
In Multiple mode deletion is blocked, while in Single mode deletion succeeds but leaves a dangling secretRef.

More Info:
The behavior depends on whether the referencing revision is active, but this is not visible to users, leading to confusing and inconsistent outcomes.