Release 1.4.0.Beta6

[michalvavrik]

Summary

Release contains:

• Bump surefire-plugin.version from 3.2.2 to 3.2.3 #979
• bump actions/download-artifact and actions/upload-artifact from v3 to v4 #991
• Bump org.apache.maven.plugins:maven-compiler-plugin from 3.11.0 to 3.12.0 #989
• Bump io.quarkiverse.artemis:quarkus-artemis-jms from 3.1.2 to 3.1.3 #990
• Make OCP config map name unique for same mount paths #992
• Support OCP secrets with destination mount path #993
• Do ci-coverage name unique for Archive Coverage Report  #994
• Set compiler release to 17 to avoid impsort compilation errors when using Java 17 features #995
• Make Dependabot bump Quarkus BOM #999
• Migrate hardcoded images to Maven properties #998
• Allow to disable Linux containers detection execution condition as it can provide false positives when Docker host strategy is used and no CLI is available #996
• Bump Quarkus to 3.6.4 #997
• Change maven-repo names to be unique #1000
• Use Quarkus Maven plugin to build native executables #971
• Bump log4j.version from 2.22.0 to 2.22.1 #1003
• Bump org.apache.maven.plugins:maven-compiler-plugin from 3.12.0 to 3.12.1 #1002
• Fix daily action - rename artifacts to just maven repo #1004
• Do not search for command line arguments during native executable build on Windows as they are not accessible via Java proccess API #1005
• Disable test failing on issue 38018 #1007
• Bump surefire-plugin.version from 3.2.3 to 3.2.5 #1006
• Bump quarkus.platform.version from 3.6.4 to 3.6.5 #1008
• Bump quarkus.platform.version from 3.6.5 to 3.6.6 #1009

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Release
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

run tests