Clarifying lacework-agent values

[soudaburger]

The original values.yaml is a bit difficult to parse and missing at least one example (when laceworkConfig.accessToken is a map, not a string). It sorts everything alphabetically and adds specific key references so that when you're traversing the YAML file, you can still understand where each key belongs.

[CLAassistant]

All committers have signed the CLA.

[cirego]

Hi @soudaburger, sorry for the delayed response. Thank you for taking the time to put together this contribution!

If you're not aware, this repository is downstream from an internal repository and is updated when we release new versions of the agent. I'm going to see what I can do to incorporate these changes into our upstream repo.

Looking at this PR, there may be another challenge adopting this. We use the yq tool to automate inserting the correct agent version into our Helm Chart and it sometimes decides to order fields / remove comments. Hopefully I can find the right incantation to make it work nicely with your improvements!

[soudaburger]

Anything you can do to get this to where it needs to go is fine by me. Appreciate the assist!