As a mesh administrator, with a mesh ("mesh 1") that is federated with one or more other service meshes ("mesh 2") - which may reside in the same cluster or a different cluster, I want to combine a service in my mesh ("service A") with a service in a different mesh ("s ervice A' ") - such that traffic directed at service A, may be handled by service A' in mesh 2 in the event that service A is not available. This creates an HA / failover relationship between the two services. These two services may have the same or different names.

The failover relationship should be one way only, unless it is configured to failover in both meshes. In the even that multiple services are aggregated together, traffic should favour the local Service A over Service A'.

Acceptance Criteria:

From mesh 1's perspective:

• Kiali should visualize that service A may also send traffic to service A' in mesh 2, showing both the service and the fact that it resides in a different mesh (with some form of mesh identifier). If the service is in a different cluster, this should also be indicated in some manner, with some form of cluster identification.
• I should be able to observe traffic (via metrics, traces) that is being handled by both Service A and Service A'. I should be able to see what % of mesh 1's traffic is being handled by Service A and Service A'. 

From mesh 2's perspective:

• Kiali should visualize that service A' may receive traffic from service A in mesh 1.... (rest is same as above).
• I should be able to observe/monitor traffic being handled by service A' that originated from mesh 1 (ie distinct from traffic that originated from mesh 2).