fix(resourcerules): add own mesh to the MeshContext, so it could be successfully resolved

[lobkovilya]

Checklist prior to review

• Link to relevant issue as well as docs and UI issues -- to[].targetRef: Mesh doesn't work, even though it shows up in Inspect API #11512
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as a image registry) and it will work on Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS --
• Tests (Unit test, E2E tests, manual test on universal and k8s) --
  • Don't forget ci/ labels to run additional/fewer tests
• Do you need to update UPGRADE.md? --
• Does it need to be backported according to the backporting policy? (this GH action will add "backport" label based on these file globs, if you want to prevent it from adding the "backport" label use no-backport-autolabel label) --

[jakubdyszkiewicz]

The code looks good but if I understand #11512 the really basic case seems to be broken. We've got here because we missed the test. Can we add it?

[lahabana]

Comment to explain we're skipping self

[lobkovilya]

Changed this code to use OtherMeshes(localMesh), probably the comment now is less needed.

[lahabana]

Why not keep the OtherMeshes method? That could make code less error prone.

[lobkovilya]

That'd require adding another field like LocalMeshName string to the Resources struct:

type Resources struct {
    MeshLocalResources ResourceMap
    CrossMeshResources map[xds.MeshName]ResourceMap
}

Given the fact at this moment we don't have constructor for Resources it increases the scope of this PR.

I can maybe add method:

func (r Resources) OtherMeshes(localMesh string) *core_mesh.MeshResourceList {
    ...
}

@lahabana @michaelbeaumont wdyt?

[lahabana]

I'd strongly argue for keeping the OtherMeshes method and adding a new Meshes method as it would make the change simpler but also makes the API less error prone