Fix inconsistency in kubernetes commands / arguments handling between jvm and native

[iocanel]

The pull request addresses the inconsitencies between jvm and native mode when it comes to command / arguments handling.

With this change the s2i builder image is no longer taken into consideration.
The command may still be generated if the user provides arguments without command.

Resolves: #24885

[gsmet]

Spotted some typos in variable names. Use your IDE to fix them as I only suggested the first occurrence.

Addressed.

[Sgitario]

Other necessary changes could be to remove the OpenshiftConfig.getEffectiveJvmArguments method which is confusing and does not add much value.
Also, we have this getEffectiveJvmArguments method in JIBConfig and S2IConfig because we had a default value for the jvmArguments, so had two properties jvmArguments and jvmAdditionalArguments. We should validate that this default value in jvmArguments and the jvmAdditionalArguments are respected after these changes.
Finally, I'm missing some tests to verify the actual change. As far I understand, before these changes, we only generated a command if we didn't know about the base image. Now, we're always generating the command if a custom jar path or the arguments are set by the user, regardless the base image we're using.
Another last note, this could be a breaking change that should be noted in the release notes.

[Sgitario]

The changes look good to me.
Moreover, I checked the reproducer in the linked issue and now the generated DeploymentConfig resource is the same for JVM and Native. So, the app should behave the same.