test(e2e): enabled federation test

[lukidzi]

Motivation

We noticed a flake. I tried to replicate it but was unsuccessful. This issue is strange because, in the test, we use kubectl apply -f config.yaml, which should override the secrets created by the controller. Additionally, apply does not return a conflict (at least, I couldn't reproduce it manually or in the test).

I believe reverting this PR might be a more reliable solution. Here's the sequence of events:

1. The user creates a Mesh with mTLS enabled.
2. At the same time, the control plane generates a certificate and key for the mesh and the user applies them using kubectl apply -f. This introduces a potential race condition.

To avoid this race condition, I think we should revert this PR.

Fix #13217

[github-actions]

Reviewer Checklist

🔍 Each of these sections need to be checked by the reviewer of the PR 🔍:
If something doesn't apply please check the box and add a justification if the reason is non obvious.

• Is the PR title satisfactory? Is this part of a larger feature and should be grouped using > Changelog?
• PR description is clear and complete. It Links to relevant issue as well as docs and UI issues
• This will not break child repos: it doesn't hardcode values (.e.g "kumahq" as an image registry)
• IPv6 is taken into account (.e.g: no string concatenation of host port)
• Tests (Unit test, E2E tests, manual test on universal and k8s)
  • Don't forget ci/ labels to run additional/fewer tests
• Does this contain a change that needs to be notified to users? In this case, UPGRADE.md should be updated.
• 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)