Investiguate switching the HTTP serialization layer from Jackson 3 to Micronaut Serialization

Investiguate switching the HTTP serialization layer from Jackson 3 to Micronaut Serialization.

During the migration from Micronaut 4 to Micronaut 5 we had to duplicate serializers and implements ad-hoc support so Kestra works with both Jackson 2 via our own JacksonMapper and Jackson 3 inside the HTTP layer so we have an idea of what it would take us to go there.

Why doing that? The obvious is better performance and better support from Micronaut as it's what they recommand. Investiguation should list the pros and cons.