chore(lint): add values.schema.json validation strict

[jon-whit]

Description

Add additionalProperties: false to the top level values.schema.json specification so that we avoid introducing new values into the values.yaml file without having explicit documentation for it.

As part of ☝️ it was brought to my attention that we didn't have some of the common Helm chart values specified in the values.schema.json, so coverage has been added for those undocumented values.

References

Added entries for the top-level subchart properties to the values.schema.json file so we can do additionalProperties: false and still pass the Helm linter. See helm/helm#10392 for more info.

Review Checklist

• I have clicked on "allow edits by maintainers".
• I have added documentation for new/changed functionality in this PR or in a PR to openfga.dev [Provide a link to any relevant PRs in the references section above]
• The correct base branch is being used, if not main
• I have added tests to validate that the change in functionality is working as expected

[jpadilla]

@jon-whit when this is ready to get merged, can we bump openfga to v1.4.0?

[rhamzeh]

Is the initContainer change breaking?

[jon-whit]

Is the initContainer change breaking?

@raghd It is, but the prior values definition seems quite misleading. The migrations job image isn't the k8s-wait-for image, that's the init container image for the migrations job. So that yaml definition, to me, was quite misleading.

[rhamzeh]

@jon-whit - yeah the new way may be better, but let's document that in the release notes, because anyone who was previously working with it will now have to update to a different config