[WIP] Add access logging support

[npolshakova]

Description

#10507

API changes

Code changes

CI changes

Docs changes

Context

Interesting decisions

Testing steps

Notes for reviewers

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[yuval-k]

why does it need to be static?

[nfuden]

any chance we can do something like https://github.com/solo-io/gloo/blob/main/projects/gloo/pkg/plugins/als/converter.go#L56-L64 to validate the contents of the access logging itself?

[npolshakova]

any chance we can do something like https://github.com/solo-io/gloo/blob/main/projects/gloo/pkg/plugins/als/converter.go#L56-L64 to validate the contents of the access logging itself?

I'm hesitant to include those initially for a couple of reasons:

1. envoy go control plane doesn't have those defined anywhere so we'd need to hard code the "unuseful" values
2. It's unclear how Gloo identified the "unuseful" commands from the envoy list. The original issue from when this code was introduced (Support listener access logging #8438) didn't seem to have it in the requirements. A bad entry shouldn't be the end of the world as long as the syntax is enclosed correctly.

Most of the validation should be happening as part of the kubebuilder validation lines. I'm not sure we want to validate on the content of access logs, just the configuration.