GH-305 Update GitHub Actions workflow to set build label for release and snapshot

[CitralFlo]

Example artifact names:
For master branch:
EternalCombat master 15

For feature/combat-rework branch:
EternalCombat feature/combat-rework - Snapshot 16

Where 15 and 16 means runner runs - making versions more distinct - GitHub does not collect and store number of runs on specific branch or pull request

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.

[CitralFlo]

Example from this branch:

[Jakubk15]

@CitralFlo Can you fix the deprecation warnings?

[Jakubk15]

I think it would also be cool to introduce a short commit hash.
Not in the GitHub Action zip file itself, but it would help, for example, in the name of a JAR file. We sometimes tend to build experimental snapshot JARs for our community members in tickets to quickly change a function in the plugin, and it would greatly help to identify the JARs instead of just having them named as 2.3.0-SNAPSHOT. The file name could look like this:
EternalCombat 2.3.0-master+cbe468c.jar