Release Verification & Required Next Steps

[jdaugherty]

This ticket is to track the various issues with the release process that have been found as part of releasing the M4. Including changes necessary to adhere to ASF policy.

1. extract the profile and confirm groovy commands are present
2. now that we have a gradle-bootstrap project, we should be able to automate the wrapper setup in the verification scripts
3. better document the bootstrap process & how to build from source; refer to that documentation in the vote email for easy access
4. document how to configure the container runtime & the container requirements for tests (https://java.testcontainers.org/features/configuration/)
5. Tomcat has a prior legal approval for some of the identical files we are including. Open a legal request to get the same approval.
6. Add steps that look at the version numbers of our CLIs and confirm they conform
7. Expand on the LICENSE/NOTICE files inside of jars
8. due to false positives, we need a way to use the fern decompiler (intellij) in verification step to minimize having to look at file.
9. mv: cannot stat 'diff_purged.txt': No such file or directory on Mac os when calling verify