feat(kumacp): mesh access log - proto + validation

[slonka]

Part of #4979

Checklist prior to review

Changelog: feat(kumacp) new mesh access log policy

• Link to docs PR or issue -- this is not implem yet so docs pr will be in that PR
• Link to UI issue or PR -- not a UI issue
• Is the issue worked on linked? -- yes
• The PR does not hardcode values that might break projects that depend on kuma (e.g. "kumahq" as a image registry) -- yes
• The PR will work for both Linux and Windows, system specific functions like syscall.Mkfifo have equivalent implementation on the other OS -- yes
• Unit Tests -- yes
• E2E Tests -- not yet, not implem
• Manual Universal Tests -- not yet
• Manual Kubernetes Tests -- not yet
• Do you need to update UPGRADE.md? -- nope
• Does it need to be backported according to the [backporting policy] (../blob/master/CONTRIBUTING.md#backporting)? -- no
• Do you need to explicitly set a > Changelog: entry here?

Changelog: feat(policy): Add MeshAccessLog policy

[lahabana]

I might have not socialized enough that we shouldn't spend time implementing kumactl for new policies. We'll do a separate task to make these not a bunch of copy paste.

[slonka]

I might have not socialized enough that we shouldn't spend time implementing kumactl for new policies. We'll do a separate task to make these not a bunch of copy paste.

@lahabana - I did not manually implement kumactl for this. I've just run make check and make test UPDATE_GOLDEN_FILES=true and that's what got generated. Otherwise those targets failed. The only files I touched manually are marked with my comments above.

[lahabana]

Ha cool :)

[slonka]

Should I change skip_registration to true?

[slonka]

I've changed it to true since it made the CI pass.

[slonka]

Should I change skip_registration to true?

@lobkovilya what are the implications of skip_registration set to true and do you know why it makes the CI crash if it's set to false?

[slonka]

Be aware of the fact that I removed reference since we agreed that for the first iteration we will not support this. This commit can be reverted when we go back to implementing it.