Kuma Version

2.9.3

Describe the bug

Whenever we try to apply HTTP related policies on remote MeshService like idleTimeout of MeshTimeout or MeshHealtchCheck the setting is not applied.

To Reproduce

Create MeshService in one zone, create client in another zone and policy with idleTimeout.

Expected behavior

Timeout should be applied

Additional context (optional)

It seems the problem is that whenever we generate clusters for MeshServices, we take protocol information from MeshContext#ServicesInformation, but we should take it directly from MeshService object.
It breaks, because when we build ServiceInformation, we infer protocol from endpoints and endpoints for remote MeshService do not have tags which is correct.
I think we should just use appProtocol from the MeshService object instead of using ServicesInformation