Create consistent Chef cookbook process

This issue is related to this OKR

Currently, our Chef cookbooks are not using their group inheritance for CI Variables. We also do not sure a consistent set of tools for the CI process of testing Chef cookbooks during MRs and merges to the main branches. While we think Chef will eventually go away, we need it to work and be easier to work with.

We have a need to enable deployments of newer Ubuntu versions with our Chef cookbooks, which requires adding the new OS to testing suites to all of the cookbooks. Using shared CI tooling would make this process easier, and get us closer to being able to deploy more modern OS' that have longer security patching support windows.