Limit the Number of Testing Runs in GH Actions

[RHammond2]

Create More Sustainable Actions Usage Through Limiting Testing Runs

This PR aims to address the lowest hanging fruit in #742 by limiting when the CI testing is run in a pull request to:

• When it is initially opened
• When it is moved out of the draft stage
• When a review is requested -- separate from the above because they may not be at the same time (rereviews also count), and the request should reflect updates made by the author
• When it is queued for merging
• Only on PRs to main or develop (no longer on pushes, i.e. new tags or release prep)
• When the actual package is updated

Section 1: Type of Contribution

• Feature Enhancement
  • Framework
  • New Model
  • Updated Model
  • Tools/Utilities
  • Other (please describe):
• Bug Fix
• Documentation Update
• CI Changes
• Other (please describe):

Section 2: Draft PR Checklist

• Open draft PR
• Describe the feature that will be added
• Fill out TODO list steps
• Describe requested feedback from reviewers on draft PR
• Complete Section 7: New Model Checklist (if applicable)

TODO:

• Ensure the limiting works

Type of Reviewer Feedback Requested (on Draft PR)

Structural feedback:

Implementation feedback:

Other feedback:

Section 3: General PR Checklist

• PR description thoroughly describes the new feature, bug fix, etc.
• Added tests for new functionality or bug fixes
• Tests pass (If not, and this is expected, please elaborate in the Section 6: Test Results)
• Documentation
  • Docstrings are up-to-date
  • Related docs/ files are up-to-date, or added when necessary
  • Documentation has been rebuilt successfully
  • Examples have been updated (if applicable)
• CHANGELOG.md
  • At least one complete sentence has been provided to describe the changes made in this PR
  • After the above, a hyperlink has been provided to the PR using the following format:
    "A complete thought. [PR XYZ]((https://github.com/NatLabRockies/H2Integrate/pull/XYZ)", where
    XYZ should be replaced with the actual number.

Section 4: Related Issues

Lowest hanging fruit of #742, but should make a useful reduction in runner usage.

Section 5: Impacted Areas of the Software

Modified Files

• .githu/workflows/ci.yml: Modifies the PR conditions under which the tests will be run. Otherwise, they should be run manually or locally.

Section 6: Additional Supporting Information

For more details on CI changes, please visit the GitHub documentation for the on event type (https://docs.github.com/en/actions/reference/workflows-and-actions/workflow-syntax#onevent_nametypes), pull_request event type (https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#pull_request), and explanations of the pull requests statuses (https://docs.github.com/en/webhooks/webhook-events-and-payloads?actionType=review_requested#pull_request).

Section 7: Test Results, if applicable

No code changes, N/A

[johnjasa]

Thanks Rob! Way to knock out the low-hanging fruit first.