Minor Version Release Docs Automation

[njtran]

Description

What problem are you trying to solve?
Our release workflow cuts a docs PR that updates the website/content/en/vX.Y folder of the new tag that's being released. This also needs to update the /website/content/en/docs folder (which is just a copy of the latest version).

This gets some things wrong. (example: https://github.com/aws/karpenter-provider-aws/pull/7519/files)

1. Doesn't include new changes to docs for the new patch version.
2. Doesn't correctly update the Charts folder
3. Upgrades the compatibility matrix incorrectly
4. Substitutes instances of ${KARPENTER_VERSION} to the version (when this should only be done on creation of a new folder)
5. Updates instances of vX.Y to main in some docs, where this should only be done for the preview version of the docs.

How important is this feature to you?
Would reduce manual work needed to be done for new patch versions of a minor version release.

• Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
• Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
• If you are interested in working on this issue or have submitted a pull request, please leave a comment