Enable custom versions for patched components

[dervoeti]

Apply a standardized SDP version suffix (3.4.1-stackable25.3.0) to all SDP artifacts that include custom modifications. This applies to JARs, Go binaries, Python packages, container images, etc.

Ensure vulnerability scanners continue detecting the original upstream version (e.g., 3.4.1 for Hadoop). This may require adding metadata, dummy components, or another approach.

[dervoeti]

Status update: It's working, but custom versions in tools can cause unexpected issues with clients, it's a breaking change. Another idea is that we have custom versions for the libraries but the binaries will have the original version, even though it's the same code. But that means we have to compile some parts of the product twice and it complicates the build process.
Another idea would be to patch the code so that it identifies to clients as the original version even though the JARs have the custom version.
We'll talk about this in a few days and decide on a way forward.