Show full container app hierarchy at every entry point

Problem

Container app nodes can appear in multiple places in the Azure resources tree:

1. Under their parent managed environment — in the Container Apps Environment subtree, the app node expands to its full hierarchy (revisions, configuration, logs, etc.).
2. Standalone — when surfaced directly via the "Container Apps" resource type group or in the Resource Group view, the app node is currently rendered as a flat leaf.

In the standalone case today, users cannot drill into the app's children (revisions, configuration, scaling, secrets, logs, …) from where the node appears. Instead, they have to navigate to the parent managed environment and find the same app there. A previous "Reveal in environment" command was added to ease this navigation, but it's still an extra hop and the standalone node remains a dead-end for inspection.

Proposed change

Render the full container app subtree at every entry point where a container app node appears — not just under the managed environment.

Requirements

• The same children (Revisions / Revision, Configuration, Logs, and everything beneath) should be shown regardless of where the container app node is parented.
• Refreshes and transient UI state must stay synchronized across copies. If a user kicks off a deploy, deletion, secret edit, revision change, etc. from one copy of the app subtree, all other copies of that subtree must reflect the new state at the same time (spinner / "Deleting…" description / children-changed refresh).
• The previously added "Reveal in environment" command becomes obsolete and should be removed.

Notes

• Tree element ids must remain unique across the two (or more) copies of the subtree, so each copy needs its own namespace of ids.
• ARM-facing identifiers (containerApp.id, managedEnvironmentId, revision.id, etc.) must remain bare/canonical — only tree-item ids are namespaced.
• A small dispatcher is needed to fan ext.state.* calls (notifyChildrenChanged / runWithTemporaryDescription / showDeleting / showCreatingChild) across every namespace so all copies update together.

Start by tracing the Container Apps Environment, Container Apps resource-type, and Resource Group tree entry points and the existing "Reveal in environment" command. Identify the shared subtree and ext.state.* update paths before introducing per-copy tree-item namespaces. Done means every entry point exposes the same children, ARM IDs stay canonical, the obsolete command is removed, and updates synchronize across copies.