Update for Service Mesh v2 and RH SSO operator

Notable Changes

Update references to user assigned SM v2 control plane instead of shared SM v1 control plane
Update references to RH SSO operator instead of community Keycloak
Switch references to service-mesh-workshop-code repo and new folder structure of config files
Update Grafana and Kiali screenshots for SMv2
Switch to beta istio security resources (i.e. RequestAuthentication and PeerAuthentication)
Update keycloak instructions (add label to allow routes to SSO and remove unnecessary reencrypt route)
Update homeroom deployment instructions
Switch homeroom image build to GitHub Action

Note:

Each user is assigned independent control plane. Previously, we provisioned independent gateways for each user, but it's not easy to do in SMv2. Additionally, previously we had shared Jaeger and Grafana instances that showed every user's services to all users. These issues are fixed with independent control planes.
Each user has a unique route to their own Jaeger/Grafana/Kiali instance so we can't use the CUSTOM_TAB in homeroom at the moment.
SMv2 is stricter with ingress. By default, SMv2 disallows any ingress traffic if it doesn't go through the istio ingress gateway. SSO has its own route, so we have to add custom labels to allow traffic.

RedHatGov / service-mesh-workshop-dashboard