Fix issues in Java Main container

[kiril-keranov]

The PR addresses some flaws, issue and peculiarities of AI generated code currently present in the Java Main container. A simple java main, non spring-boot, application can be staged successfully with the current implementation with certain drawbacks and issues:

• The container security provider and client certificate mapper dependencies are currently omit from the classpath when starting the java main( non spring-boot ) app. They are now added accordingly.
• Missing logic for searching java main class in jar in findMainClass marked with TODO is now addressed.
• Building the classpath of the startup command is now adjusted with corresponding profile.d script instead of overwriting the CLASSPATH variable that cleaned adding to to CLASSPATH by other frameworks participating in the application staging process. Also the paths to the jar dependendencies added to to the startup classpath are corrected.