docs(meshtls): design of MeshTLS

[slonka]

Checklist prior to review

https://docs.google.com/document/d/1zA1q1hD3PN7c1EsnxkwggtBR08-8i5voZG3yNJyjQfI/edit#heading=h.n6cmlf1eel2z

• Link to relevant issue as well as docs and UI issues -- closes Design MeshTLS policy #4622
• 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) --

[michaelbeaumont]

Just had one comment about making sure the schema is clear for the chosen option compared to other example resources.

[slonka]

@lobkovilya please approve here or as you did in the doc