Investigate whether LSP4Jakarta consistently processes fully qualified class names.

[mrglavas]

• Check whether LSP4Jakarta has the correct behaviour for applications if they specify a fully qualified class name instead of their simple name (e.g. @jakarta.ws.rs.PUT vs @PUT).
• Check whether LSP4Jakarta unambiguously matches the expected class names when checking diagnostics, applying quick fixes, etc... (e.g. @jakarta.ws.rs.PUT vs @my.random.pkg.PUT).

Note: We're noticing inconsistencies in the processing of qualified names in the code actions / quick fixes in Liberty Tools for IntelliJ and that code was ported from LSP4Jakarta.

[mrglavas]

A couple more tasks for this item:

• Check for usage of DiagnosticUtils.getSimpleName(). Investigate how it's being used to shorten qualified names and determine if that usage is problematic or may become a problem in the future as Jakarta EE evolves.
• Review the diagnostic collectors, checking if there are any other methods being used for shortening qualified names.

[mrglavas]

Should check whether the issues (in Liberty Tools for IntelliJ) with qualified names being tracked here: OpenLiberty/liberty-tools-intellij#879 also apply to this project.