enhancement(kubernetes platform): add the ability to configure Vector API at the Helm charts

[dzirg44]

According to the #6227 I implemented helm api endpoint configuration.
I am not sure in the current implementation, because it looks a "little bit" weird ))
But I couldn't make up something better.
Also I am not so confident in grammar and will be glad to fix my mistakes.

[MOZGIII]

Thanks a lot for preparing a PR for us!

This implementation is too complicated, and I suggest we go with a more direct one - as I mention in the comment I left above.

[dzirg44]

I made it simpler, but maybe we have to check if we have api vars or not?
or just add default variables to the ?
https://github.com/timberio/vector/blob/master/distribution/helm/vector-agent/values.yaml

[MOZGIII]

Yeah, vector-agent should have the vars too. It makes sense, cause any vector instance can serve the API.

[dzirg44]

fixed, also my linter found some wrong whitespaces here , i can delete or keep it.

[dzirg44]

fixed, thank you for your patience )

[dzirg44]

should I squash commits or you will?

[MOZGIII]

I'll take care of the squash (in fact, Github will do it for us automatically).

[MOZGIII]

Looks good, all that's left is making the checks pass.
You need to:

• sign your commits with DCO (see https://github.com/timberio/vector/blob/master/CONTRIBUTING.md#signing-off)
• run make update-kubernetes-yaml and make update-helm-snapshots and commit the resulting changes

[dzirg44]

Done.

[MOZGIII]

Great, checks are passing! I've left some final touches, and we can merge after they're fixed!
Thanks a lot for your contribution!

[dzirg44]

Changed! Thank you for mentoring!

[MOZGIII]

Thanks for the contribution!