Add separate "Jakarta [format] provider"s for 2.13

[cowtowncoder]

Due to conundrum of #132 and related, I started thinking that perhaps "hard fork" is what we need.
For background, see these 2 isssues:

• (on naming wrt Jakarta): Request for distinguishing acronym for "Jakarta XML Binding", different from JAXB jakartaee/jaxb-api#179 -- should this be called "jakrs" (or jakarta-rs)?
• (on similar fork of JAXB annotations): Add Jakarta-variant of "JAXB" annotations: jackson-module-jakarta-xmlbind-annotations jackson-modules-base#130

With that, I am thinking that copying a subset of existing components might make sense:

• Usage of JAX-RS providers very lopsided: 96+% just use json-provider (3.8 million d/l per month)
• Other providers barely used: second is XML with 80k d/l per month; similarlyjackson-datatype-jaxrs is barely used

So, in fact, we could simply start by only porting base and json-provider.

An added bonus is that some of deprecated methods could be removed: in fact, I'd probably just drop Annotations abstraction (already done for 3.0).

[cowtowncoder]

This has been implemented, see #146, resulting in:

https://github.com/FasterXML/jackson-jakarta-rs-providers/