Prevent that latest release version can communicate with `main` branch

[elfenpiff]

Observed result or behaviour:
Currently, it is possible that the latest release version can connect to any other process that uses current iceoryx2 main, even when they are not compatible.
The cause originates in https://github.com/eclipse-iceoryx/iceoryx2/blob/main/iceoryx2-bb/elementary/src/package_version.rs which is stored in shared memory. If both u64 values are identical, iceoryx2 connects both instances. The latest main branch has still the v0.6.1 major, minor, patch value backed in and therefore they can connect.

The package version uses an u64 as underlying data type with u16 for major, minor and patch. So we have 16 bits left to mark any other internal deviation, like the current main based on v0.6.1. By setting the 16 bits to u16::MAX for instance.

Expected result or behaviour:
The user gets an error that states that the iceoryx2 main branch is not compatible with the latest release.

[FerdinandSpitzschnueffler]

Seems related to #843

[elBoberido]

@FerdinandSpitzschnueffler indeed. I think one of these should be closed

@elfenpiff if we go with the u64 approach, I would suggest to use the MSB as indicator for the dev version. This ensures that the dev version is always higher than a released version