Create method to track items that need to be updated for new version number when code is changed in VERDI

[lizadams]

Is your feature request related to a problem? Please describe.
To patch VERDI for the log4j release, new code is required, which requires an update to the version number according to Donna Schwede.
"Our CMAQ development SOP and QAPP call for a change in the version number when a change is made in the code. Following that guidance and for full traceability, we should be releasing VERDI 2.1.1 rather than tracking with a data stamp."

Describe the solution you'd like
Identify what needs to be changed in github for each new release number.

Documentation update is required with a new version number:
VERDI_2.1/plugins/bootstrap/help/VERDIUserManual2.1.pdf
Does new documentation need to be created with each minor version number?

Following files reference the version number:
VERDI_2.1/INSTALL.mac.txt
VERDI_2.1/RELEASE-NOTES.txt (release notes need to be updated and version number changed)
VERDI_2.1/config.properties.TEMPLATE

Where in the code does the Help> About popup window get updated?

Need to update version number on CMAS Center Website and upload packages to the google drive.
https://cmascenter.org/verdi/

Need to update the announcement on CMAS User Forum.

Need to send updated release announcement to the CMAS Listserve.

Describe alternatives you've considered
We need a checklist to identify where the version number needs to be updated.

Additional context
Add any other context or screenshots about the feature request here.

[systemsgo]

The about box is automatically updated based on the value in build.dist.. INSTALL.mac.txt and config.properties.TEMPLATE will now be updated using the same mechanism. Release Notes and the user manual will still need to be manually updated.