Final attempt to improve deployment workflows

[hohwille]

While I was stumbling over this topic again with my PR #562 I want to finally get this topic done once and for all.
I thought I had made my goals clear with #427 but this issue was closed while important aspects were never implemented.

• In the matix OS build all we should do is compile the code and build the native image - no documentation, not test, no packaging/assembly or whatever. That native image should be uploaded via github action upload as executable (not as tar.gz archive) to ${matrix-os}/ideasy[.exe].
• In the main build we should download the native images via github action download and then trigger the full deployment build. Here the assembly should be build and then be attached as artifact. These assembly can be changed so that they refer the native image directly from the downloaded directory ${matrix-os}/ideasy[.exe] so we do not need additional mapping in the github actions scripts. No need for build-helper-plugin and pointless file-mappings.
• rename the assembly files to reasonable filenames again as they are not connected to ${matrix.os} anymore. So release-win-x64.xml, release-mac-arm.xml, etc.
• ensure to update the pom.xml so all assembly descriptors are run during the build. You do not even need to list them all: https://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html#descriptorSourceDirectory
• We aggreed that the entire build process gets documented as already described in Improve deployment workflows (nightly and release) #427 but never implemented yet.

This ticket shall not be closed before all tasks are implemented (or moved to other tickets that do not get closed before implemented).
Sorry for saying the obvious but it seemed necessary.