Consider United Message Encode/Decode Conversion

Record support is a big feature in Jakarta EE 11.

Unfortunately, when I tried to update my Cargotracker to Jakarta EE 11 and replace the Persistence `@Embeddedable` class with a record class, but I found if a `record` field exists in the JMS payload, it will cause an exception that indicates the record class did not implement `Serializable`.

I would like there exists a united message codec infrastructure to encode/decode varied formats or Mediatypes (JSON, XML, Corb, Probuff, etc), and make the current HTTP/Messaging specifications including REST, WebSocket, JMS, and future RPC, etc. adapt the same MessageCodecs to handle the encoding/decoding work like what it does in the new Spring WebFlux stack.

And make it configurable like spring boot [`CodecsCustomizer`](https://www.google.com/search?q=Codecs+Customizer+spring+boot&client=firefox-b-d&sca_esv=6434efe0858f7e50&sxsrf=AHTn8zooiObvQM_L_3_8YgcvkPj49gKKjw%3A1737684088402&ei=ePSSZ7OpGLTJkPIPpe-WuAY&ved=0ahUKEwizxcjWoY2LAxW0JEQIHaW3BWcQ4dUDCBI&uact=5&oq=CodecsCustomizer+sprng+boot&gs_lp=Egxnd3Mtd2l6LXNlcnAiG0NvZGVjc0N1c3RvbWl6ZXIgc3BybmcgYm9vdDIEEAAYRzIEEAAYRzIEEAAYRzIEEAAYRzIEEAAYRzIEEAAYRzIEEAAYRzIEEAAYR0j_EVAAWABwAHgCkAEAmAEAoAEAqgEAuAEDyAEAmAIBoAIVmAMA4gMFEgExIECIBgGQBgiSBwExoAcA&sclient=gws-wiz-serp).

No files or tests are named. Start by comparing the Jakarta EE REST, WebSocket, and JMS specifications with Spring WebFlux's codec customization; done would require an agreed, configurable codec architecture covering the listed message formats and specifications.

Written by the indexing model from the issue text.