ENH: Use latest actions, do not pin to latest version

The convention of only specifying the MAJOR version
is the indicator that the latest version in that
series should be used.

By not specifying the MINOR and PATCH, the exact versions
is not pinned, but the latest in that series is chosen.
(i.e. the v5 tag is updated every time a new MINOR or PATCH
tag is generated).

This allows benefiting from minor patch fixes without needing
to update workflows.

Author: hjmjohnson

.github/workflows/build-test-publish.yml

@@ -27,12 +27,12 @@ jobs:
             cmake-build-type: "MinSizeRel"
 
     steps:
-      - uses: actions/checkout@v4.2.2
+      - uses: actions/checkout@v4
         with:
           path: Ex
 
       - name: Set up Python 3.11
-        uses: actions/setup-python@v5.4.0
+        uses: actions/setup-python@v5
         with:
           python-version: 3.11
 
@@ -151,12 +151,12 @@ jobs:
             cmake-build-type: "MinSizeRel"
 
     steps:
-      - uses: actions/checkout@v4.2.2
+      - uses: actions/checkout@v4
         with:
           path: Ex
 
       - name: Set up Python 3.11
-        uses: actions/setup-python@v5.4.0
+        uses: actions/setup-python@v5
         with:
           python-version: 3.11
 
@@ -237,9 +237,9 @@ jobs:
         os: [ubuntu-24.04, windows-2022, macos-13]
 
     steps:
-      - uses: actions/checkout@v4.2.2
+      - uses: actions/checkout@v4
       - name: Set up Python 3.11
-        uses: actions/setup-python@v5.4.0
+        uses: actions/setup-python@v5
         with:
             python-version: 3.11
 
@@ -271,13 +271,13 @@ jobs:
             cmake-build-type: "Release"
 
     steps:
-      - uses: actions/checkout@v4.2.2
+      - uses: actions/checkout@v4
         with:
           path: Ex
           submodules: recursive
 
       - name: Set up Python 3.11
-        uses: actions/setup-python@v5.4.0
+        uses: actions/setup-python@v5
         with:
           python-version: 3.11