Add ability to drill down into replicas/containers

This is needed for attaching log stream and connecting a console, as they both need to select the replica to use.

Replicas return this information:

{
    "id": "/subscriptions/.../resourceGroups/.../providers/Microsoft.App/containerApps/.../revisions/antchu-test--144079l/replicas/antchu-test--144079l-7b754df4fd-cb8hf",
    "name": "antchu-test--144079l-7b754df4fd-cb8hf",
    "properties": {
        "containers": [
            {
                "containerId": "containerd://4312e8a562c10fcdf8820caa28ee981c19ecc46eba145460035550319bd081f7",
                "name": "antchu-test",
                "ready": true,
                "restartCount": 0,
                "started": true
            },
            //...
        ],
        "createdTime": "2022-03-14T04:51:15Z"
    },
    "type": "Microsoft.Web/containerapps/revisions/replicas"
}

Need to see if replicas have an overall status or other interesting info to display, so that the user can figure out what replica to connect to and diagnose. Otherwise maybe find a way to display details from containers. Note that some system sidecar containers might appear. Need to understand if we can/should filter them out.

The log stream and console commands might actually need to specify a container, not just a replica.

Start by tracing the existing replica and container resource views, then inspect the log-stream and console commands that need a replica or container selection. Determine what replica status and container details the Azure API exposes, including whether system sidecars should be filtered. Done means users can identify and select the appropriate replica and container for diagnostics.