New lightning project.yaml variables can break CLI deployment

New project-level features add new variables to the project.yaml. When this happens, the CLI must be updated to support the variables so that cli operations can run without breaking. This is a recent report of this bug.

We think fixing this will be expensive but we have a few ideas on how we might pay the debt sustainably.

Potential solutions

1. Add compatibility to documentation to help users know which cli version is compatible with lightning version.
2. Update the extraneous parameter error message to suggest updating cli- version.
3. Add a sentry alert log for extraneous parameter error
4. Limit the variables exported by project.yaml per time based on CLI compatibility. "don't export concurrency and collections if you are on this CLI version because deploy will break."