CI: Do not run deployment / specs when only documentation is changed
Currently, all changes are pushed through the CI pipelines. This can result in resource consumption when there are no functional changes to the charts themselves, especially documentation only changes.
We should not be consuming resources in our clusters for such changes.
A complete CI pipeline is run, including review deployments into EKS & GKE, when changes are made unrelated to functionality.
See !849 as a current example.
Deployment & testing stages are skipped when only documentation is updated. (Skip