Maureen would like to validate a minor update to a module won't destroy existing resources

This feature consists of two parts:

1. Clearly document the guidelines for what changes require/constitute a major/minor/patch release
2. To the extent that it is possible, the PR validation process should validate the applied release label to make sure it is compliant to the guidelines. At a minimum, assuming that part of the expectation for a minor release is that it won't destroy existing resources when the new version is applied, the validation process needs to validate.