ci: unify workflow names (follow file name)

.github/workflows/ASSIGN_MILESTONE.yml

@@ -1,4 +1,4 @@
-name: Assign Milestones
+name: ASSIGN_MILESTONE
 
 on:
   issues:

.github/workflows/CODE_SCANNING.yml

@@ -1,5 +1,4 @@
-
-name: "Code Scanning"
+name: CODE_SCANNING
 
 on:
   push:

.github/workflows/CREATE_MILESTONE.yml

@@ -1,4 +1,4 @@
-name: Create new Milestone
+name: CREATE_NEW_MILESTONE
 
 on:
   milestone:

.github/workflows/NEW_ALPHA_ISSUE.yml

@@ -1,4 +1,4 @@
-name: Add Alpha version reminder
+name: NEW_ALPHA_ISSUE
 on:
   schedule:
     # After the April and October releases
@@ -19,4 +19,4 @@ jobs:
             - [ ] Update linting profiles (C7, C8)
 
             ### Why should we do it?
-            To support the next alpha release of the engine.
+            To support the next alpha release of the engine.

.github/workflows/NEW_MAJOR_ISSUE.yml

@@ -1,4 +1,4 @@
-name: Add Major version reminder
+name: NEW_MAJOR_ISSUE
 on:
   schedule:
     # Before the April and October releases
@@ -17,4 +17,4 @@ jobs:
             Mark the latest alpha versions as stable.
 
             ### Why should we do it?
-            In the next release cycle, the current alpha versions will be relased as stable.
+            In the next release cycle, the current alpha versions will be relased as stable.

.github/workflows/PUBLISH_RELEASE.yml

@@ -1,4 +1,4 @@
-name: 'Publish release'
+name: PUBLISH_RELEASE
 on:
   release:
     types:

.github/workflows/RELEASE_ISSUE.yml

@@ -1,4 +1,4 @@
-name: Release Issue
+name: RELEASE_ISSUE
 on:
   issues:
     types: [closed, assigned]