feat: Ensure extension is created with camel-base metadatas

[gansheer]

Ref #5191
Ref quarkusio/quarkus#35404

Add the 'integrates' new metadata field filled by default with camel-base artifact reference with a version referencing the property. version: "${camel.version}" stays as-is in source (NOT replaced).

Then the version value is added by the maven-resources-plugin. The changes in build:

• Applies to the implicit default-resources execution
• Says: "Copy everything from src/main/resources EXCEPT META-INF/quarkus-extension.yaml"
• Other files (like quarkus-extension.properties) are still copied normally

The Maven Build Process does the following:

1. Default Resources (default-resources execution)
   Process: src/main/resources/**
   EXCEPT: META-INF/quarkus-extension.yaml (excluded)
   Result: Other files copied to target/classes/

2. Legal Resources (legal-resources execution)
   Copies license files with filtering

3. Filter Extension Metadata (filter-extension-metadata execution)
   Process: ONLY META-INF/quarkus-extension.yaml
   Filtering: true
   Reads: "${camel.version}" from pom properties
   Replaces: "${camel.version}" → "4.19.0"
   Result: Filtered file in target/classes/META-INF/

[gansheer]

I will resolve the conflict when the PR review is done.

[zbendhiba]

LGTM!

[gansheer]

Adapted to new design: quarkusio/quarkus-platform-bom-generator#415 (comment)

[ppalaga]

Suggested change

	<resources>
	<resource>
	<directory>${project.basedir}/src/main/resources</directory>
	<excludes>
	<exclude>META-INF/quarkus-extension.yaml</exclude>
	</excludes>
	</resource>
	<resources>
	<resource>
	<directory>${project.basedir}/src/main/resources</directory>
	<excludes>
	<exclude>META-INF/quarkus-extension.yaml</exclude>
	</excludes>
	<filtering>false</filtering>
	</resource>
	<resource>
	<directory>${project.basedir}/src/main/resources</directory>
	<includes>
	<include>META-INF/quarkus-extension.yaml</include>
	</includes>
	<filtering>true</filtering>
	</resource>

You can do it all in one block

[jamesnetherton]

What's the status of this? Is it mergeable? Or are we waiting on something from the Quarkus side?

[gansheer]

What's the status of this? Is it mergeable? Or are we waiting on something from the Quarkus side?

Let me squash correctly first for ease of backport.

[gansheer]

@jamesnetherton It's good for me now.

[apupier]

@gansheer there are conflicts to resolve

[jamesnetherton]

Is this safe to merge without the associated Quarkus issues being complete?

[gansheer]

Is this safe to merge without the associated Quarkus issues being complete?

Let's wait, that's probably safer.

[gansheer]

Waiting for next release of https://github.com/quarkusio/quarkus-platform-bom-generator.