ci: more consistent workflow names

.github/workflows/linux-arm32v7.yml

@@ -1,4 +1,4 @@
-name: build linux static arm32v7
+name: linux-arm32v7 CI binaries
 
 on:
   push:

.github/workflows/linux-x64.yml

@@ -1,4 +1,4 @@
-name: build linux static x64
+name: linux-x64 CI binaries
 
 on:
   push:

.github/workflows/mac.yml

@@ -4,7 +4,7 @@
 # using GHC 8.6,
 # and uploads a binaries artifact.
 
-name: mac CI
+name: mac CI binaries
 
 on:
   schedule:

.github/workflows/pull.yml

@@ -11,7 +11,7 @@
 # This is the "master" workflow on which the others are based, 
 # with the most detailed notes.
 
-name: pull CI
+name: pull request CI
 
 on:
   # Scheduled workflows run on the latest commit on the default or base branch. (master)

.github/workflows/release.yml

@@ -1,10 +1,10 @@
-# Runs on push of a [0-9]* or r[0-9]* tag (to any branch ?)
+# Runs on push of a [0-9]* or r[0-9]* tag (to any branch ?) 
 
 # Creates a draft github release.
 # See https://github.com/actions/create-release, still pretty rough as of 20200609.
 # see also: https://github.com/marketplace/actions/tag-release-on-push-action
 
-name: release
+name: create release
 
 # https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#onpushpull_requestbranchestags
 # also: "The action does not seem to work for tags created before the workflow."

.github/workflows/windows.yml

@@ -3,7 +3,7 @@
 # Builds all modules optimised on windows,
 # and uploads a binaries artifact.
 
-name: windows CI
+name: windows CI binaries
 
 on:
   schedule: