javax --> jakartaee namespace transition - Ecosystem tracking

This issue is the umbrella issue for setting up a tracking system to track the javax to jakarta namespace changes in the ecosystem (popular libraries, frameworks, tools, servers, etc).

**--> Please feel free to edit [The Tracking Sheet](https://docs.google.com/spreadsheets/d/1gEv8IK2xXYJxf2i0uUCwfIBMPybF9XMOczhA--hdRaE/edit?usp=sharing) <--**

Plan for enabling javax -> jakarta adoption by ecosystem

* Application Servers
* Web Servers
* MicroProfile implementers
* IDEs
* Frameworks
* Monitoring tools
* Testing tools
* Porting tools
* Cloud Providers

Highlight compatibility success stories (e.g. Eclipse Transformer, application migrations)
Evaluate compatibility options, e.g. “legacy” profile, or “MP” profile
Monitor/measure progress for tools targeted for supporting Jakarta EE 9+

Start with the linked Tracking Sheet and the issue's ecosystem categories, including application servers, frameworks, IDEs, testing tools, and cloud providers. Define the tracking system around javax-to-jakarta adoption, compatibility success stories, compatibility options, and progress for Jakarta EE 9+ tools; done requires a usable, maintained overview.

Written by the indexing model from the issue text.