update cmakelists for release.

[dholladay00]

PR Summary

Prepare for release!

@Yurlungur @jhp-lanl @rbberger @mauneyc-LANL

PR Checklist

• Adds a test for any bugs fixed. Adds tests for new features.
• Format your changes by using the make format command after configuring with cmake.
• Document any new features, update documentation for changes made.
• Make sure the copyright notice on any files you modified is up to date.
• After creating a pull request, note it in the CHANGELOG.md file.
• LANL employees: make sure tests pass both on the github CI and on the Darwin CI

If preparing for a new release, in addition please check the following:

• Update the version in cmake.
• Move the changes in the CHANGELOG.md file under a new header for the new release, and reset the categories.

[jhp-lanl]

Before the release, can we take a hard look at our package.py and make sure the dependencies make sense. Basically I want to make sure the correct things are pointing @1.9.0 rather than @main.

For example:

depends_on("[email protected]:", when="@main +tests")

should be

depends_on("[email protected]:", when="@1.9.0: +tests")

I think, right?

I also put in the ports-of-call 1.6.0 dependency, but I chose a non-existent version number:

depends_on("[email protected]:", when="@1.8.1:")

I think those are the only two things that might need looking at.

[jhp-lanl]

Before the release, can we take a hard look at our package.py and make sure the dependencies make sense. Basically I want to make sure the correct things are pointing @1.9.0 rather than @main.

I should add, this can be done separate from this MR if need be

[Yurlungur]

Other than @jhp-lanl 's concerns LGTM

[jhp-lanl]

@rbberger can you take a look at the package.py and make sure my comments are correct and/or whether we need any other changes before release.

[jhp-lanl]

Other than updating the changelog, this looks good to me!

[dholladay00]

This is ready @Yurlungur @jhp-lanl