Weekly Builds/Testing to Verify Functionality

[zachcran]

Is your feature request related to a problem? Please describe.
When CMake increments versions underneath CMakePPLang, there is a chance that it will break some of our functionality. There is not a great indicator on the repository for whether CMakePPLang currently is working with the latest version of CMake.

Describe the solution you'd like
I propose that we schedule a weekly build/test action on the repository that builds with the latest CMake version and latest release candidate version. Then, badges for the tests will be added to the README so they display on the main CMakePPLang repository page to give an at-a-glance view of whether CMakePPLang is currently functioning with the latest CMake version. The release candidate test can also serve as an early warning system for if the next version of CMake is going to cause issues for CMakePPLang.

Describe alternatives you've considered
Currently, when a new version of CMakePPLang is merged in, it is tested against the latest CMake version, latest release candidate version, and lowest supported CMake version. Therefore, in the time frame between a CMakePPLang release and the next CMake release, we can verify that CMakePPLang will work as expected. This check is invalidated as soon as a new CMake version is released, though, so it is not reliable in cases where there is a long period of time between CMakePPLang releases.

If a new CMake version releases, one can also manually install the latest CMake version and run CMakePPLang's tests, although this is cumbersome and requires users to commit to learning enough to build and test CMakePPLang just to know if it is currently working and worth using.