Test BootableJar using Channel Manifest

[tommaso-borgato]

This PR:

• reintroduces bootable jar tests
• adds option to run bootable jar tests with a channel manifest

[liweinan]

The test failures seem to be related with the galleon update.

[tommaso-borgato]

@jbliznak can you have a look?

[liweinan]

I guess after @jamezp comes back he will check this.

[tommaso-borgato]

just re-base on main and with both main and this branch I get:

$ mvn clean install -DskipTests
...

[ERROR] Failed to execute goal on project resteasy-core-spi: Could not resolve dependencies for project org.jboss.resteasy:resteasy-core-spi:jar:7.0.0.Alpha2-SNAPSHOT: The following artifacts could not be resolved: jakarta.ws.rs:jakarta.ws.rs-api:jar:4.0.0 (absent): jakarta.ws.rs:jakarta.ws.rs-api:jar:4.0.0 was not found in https://repository.jboss.org/nexus/content/groups/public/ during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of jboss-public-repository-group has elapsed or updates are forced -> [Help 1]
...

[jamezp]

We can talk offline about this, but I need to understand the motivation behind this. I've got some opinions on how we test the bootable JAR that I might share alone, but I don't think we do it right :)