jlink should create the jimage file in the native endian for the target platform

jlink accepts `--endian <little|big>` option to specify the byte order of the jimage file. This requires the user's help to generate a run-time image targeted for a platform different than the build platform.

We should consider jlink to determine the endianness from the target java.base module and drop `--endian` option. The `ModuleTarget` attribute is not enough but a short term fix might be for jlink to map the known ModuleTarget values to endianness.

See the discussion in https://git.openjdk.org/jdk/pull/11943