Evaluate alternatives to JNDI for eventual deprecation

**Is your feature request related to a problem? Please describe.**
JNDI is not the strategic way that things should be looked up in Jakarta. CDI should be the normal way to look things up.

**Describe the solution you'd like**
Evaluate use of JNDI in the platform spec and component specs to see if CDI-based alternatives exist and if they do consider deprecating JNDI usage in the platform and component specifications. If an alternative doesn't exist research to see if one can be created.

Start by reviewing JNDI usage across the Jakarta EE platform and component specifications, then identify CDI-based alternatives where they exist. Document which usages could be deprecated and where no alternative exists, including whether a new alternative should be researched. Done means the evaluation and recommendations are recorded.

Written by the indexing model from the issue text.