[Feature] Enhancements to the Build and Release GitHub Workflows

### Description of the Feature

The Build (`build.yaml`) and Release (`release`) pipelines are solid after thoughtful implementation, thorough testing, and AI code reviews as part of GH-2. However, there are opportunities for improvement:

1. The build number (**45** in this example: entropy-1.2.3-ALPHA.**45**-macos.jar) in artifact outputs of the Build pipeline is based on the GitHub Workflow run number. This works well when only utilizing the Build pipeline, but if the Release pipeline calls the Build pipeline it uses the run number from the Release pipeline, which could cause confusion and potential conflicts.
There are two potential solutions. We could either: replace the workflow call with the GitHub CLI to call the Build workflow as a separate run that's not associated with the Release workflow; or we could store the build number in a separate location, and for each build, call & increment the number and use it for the file output.
2. Output release information to Discord (this would likely be my personal Discord server at first, but may be moved to a dedicated "Entropy" Discord server.
3. Platform sanitation allows for partial matches of platforms: `linux1` is valid after sanitation, even though it wont run a build for any platform.
4. Additional optimizations and improvements can be investigated as part of this story (cache improvements, pipeline optimizations, etc.).

### Benefits of the Feature

This feature would make for more robust workflows, potentially improve performance, and increase visibility on release failures/successes.

### Additional Information

_No response_