build: rename since coverage is only collected for changed packages.

In contrast to the workflows to run examples, benchmarks, and tests for
all packages affected by the changes in a PR or push, the workflow to
collect coverage is only run for the changed packages themselves. This
renaming makes this clearer.

.github/workflows/run_affected_tests_coverage.yml → .github/workflows/run_tests_coverage.yml

@@ -17,7 +17,7 @@
 #/
 
 # Workflow name:
-  name: run_affected_tests_coverage.yml
+  name: run_tests_coverage.yml
 
   # Workflow triggers:
   on:
@@ -48,7 +48,7 @@
     workflow_dispatch:
       inputs:
         directories:
-          description: 'List of changed directories for which to run affected tests (space separated):'
+          description: 'List of changed directories for which to run tests (space separated):'
 
   # Workflow jobs:
   jobs:
@@ -57,7 +57,7 @@
     coverage:
 
       # Define a display name:
-      name: 'Calculate test coverage for affected packages'
+      name: 'Calculate test coverage for packages'
 
       # Define the type of virtual host machine:
       runs-on: ubuntu-latest
@@ -133,7 +133,7 @@
             else
               directories="${{ steps.changed-directories.outputs.directories }}"
             fi
-            . "$GITHUB_WORKSPACE/.github/workflows/scripts/run_affected_tests_coverage" "$directories"
+            . "$GITHUB_WORKSPACE/.github/workflows/scripts/run_tests_coverage" "$directories"
           timeout-minutes: 30
 
         # Extract coverage values and assign to output:

.github/workflows/scripts/run_affected_tests_coverage → .github/workflows/scripts/run_tests_coverage

@@ -18,7 +18,7 @@
 
 # Script to calculate package test coverage for a given list of changed files.
 #
-# Usage: run_affected_tests_coverage file1 [file2 file3 ...]
+# Usage: run_tests_coverage file1 [file2 file3 ...]
 #
 # Arguments:
 #