Change build rules to not double fire on PRs

[peterfpeterson]

Description

By reducing which pushes fire CI to only the default branch and version tags, PR builds will not get two versions of each build.

The documentation for being more specific on branches/tags for a push is here.

Refs #2378

How Has This Been Tested?

Look at builds on #2647 for comparison (36 builds). This does not have builds for push, only pull_request is present (18 builds).

Review Checklist (please remove items if they don't apply):

• Code has been reviewed
• Functionality has been tested
• Windows installer (GH artifact) has been tested (installed and worked)
• MacOSX installer (GH artifact) has been tested (installed and worked)
• User documentation is available and complete (if required)
• Developers documentation is available and complete (if required)
• The introduced changes comply with SasView license (BSD 3-Clause)

[krzywon]

Thanks for the contribution, @peterfpeterson. I triggered the CI for you.

We have an outstanding issue related to this - Fixes #2378.

[peterfpeterson]

Related to the issue mentioned, this change reduces what is run in the overall workflow. The individual tasks can be filtered down to run on particular triggers as well. When doing that, I recommend always including a workflow_call or workflow_dispatch on the item so they can be triggered by hand.

[wpotrzebowski]

Does this trigger CI only for the pushes to 'main' branch only? Personally,I look at CI runs for any branch (without opening PR), however, this indeed may be a waste of resources

[peterfpeterson]

Correct. If you add workflow_dispatch you can also press a button in "actions" to launch a build on any commit/branch/whatever.

[wpotrzebowski]

I am fine with merging it as it is and then make adaptations to workflow if necessary