Add apicurio jsonserde support

[carlesarnal]

This PR includes the initial support for json schema serialization using Apicurio Registry serdes. For now, autodiscovery of the channel and appropriate serde is not possible, so it must be manually configured.

[carlesarnal]

@cescoffier do you mind approving the CI run? I have the quickstart ready locally and the tests passing for native as well.

[gsmet]

@carlesarnal hey, thanks for this PR. Ideally, make sure CI passes in your fork before we approve the CI run here.

Also, probably a good idea to squash the commits to be a bit more semantic. Not sure if you need one big one or several ones but we don't need to see all the small iterations.

Thanks!

[carlesarnal]

@carlesarnal hey, thanks for this PR. Ideally, make sure CI passes in your fork before we approve the CI run here.

Also, probably a good idea to squash the commits to be a bit more semantic. Not sure if you need one big one or several ones but we don't need to see all the small iterations.

Thanks!

Hey, yes, I realised now that the CI jobs are running on my fork, I'll make sure they pass there and squash the commits, tyvm.

[github-actions]

🙈 The PR is closed and the preview is expired.

[carlesarnal]

@gsmet all the tests are green on my fork except for the JVM 17 on Windows that, for some reason cannot find a valid docker env. Any hint on what might be happening?

[carlesarnal]

@gsmet all the tests are green on my fork except for the JVM 17 on Windows that, for some reason cannot find a valid docker env. Any hint on what might be happening?

Ok, I might have figured out the reason, I was defaulting the test execution to true no matter the profile, I have changed the default values appropriately, let's see what CI has to say, sorry about the noise.

[carlesarnal]

@cescoffier at your convenience, CI on my fork is green, including native tests etc, so this is ready for your review. Thanks.

[cescoffier]

LGTM

It would be great to:

1. implement serde discovery if possible (not totally sure it it possible)
2. Make sure native is working as expected.

[carlesarnal]

LGTM

It would be great to:

1. implement serde discovery if possible (not totally sure it it possible)
2. Make sure native is working as expected.

1. It may be possible by making it depend on the schema location property since that property is only configurable for the json schema serializer. I would need some guidance on how to implement it.
2. Native is working fine so far, the tests have been included in the native tests json and are passing on my fork and I already have the quickstart ready here and the native tests is passing there as well with no issues with a local build of Quarkus. The only requisite in this case is to add the json schema that will be used for serialization to the quarkus.native.resources.includes property, something like this.

[quarkus-bot]

Failing Jobs - Building bbee606

Status	Name	Step	Failures	Logs	Raw logs	Build scan
✔️	JVM Tests - JDK 17					🚧
✖	JVM Tests - JDK 21	Build	Failures	Logs	Raw logs	🚧

Full information is available in the Build summary check run.

Failures

⚙️ JVM Tests - JDK 21 #

- Failing: extensions/scheduler/deployment 
! Skipped: extensions/quartz/deployment extensions/spring-scheduled/deployment integration-tests/main and 7 more

📦 extensions/scheduler/deployment

✖ io.quarkus.scheduler.test.PausedSchedulerTest.testSchedulerPauseResume line 47 - More details - Source on GitHub

org.opentest4j.AssertionFailedError: expected: <false> but was: <true>
	at org.junit.jupiter.api.AssertionFailureBuilder.build(AssertionFailureBuilder.java:151)
	at org.junit.jupiter.api.AssertionFailureBuilder.buildAndThrow(AssertionFailureBuilder.java:132)