Run Diagnostics on the relevant Annotations for Persistence about lsp4jakarta

[kathrynkodama]

This is a very generic issue. We should open individual issues for each of the diagnostics (similar to how we did for Servlet)

[AnkushSharma2698]

There is not many use cases where users are extending a class and that I must check for the existence of some extending class in the class def. Rather I believe the diagnostics I will need on annotations will be related to imports.

So I will be creating Annotation diagnostics for the following:

@Entity
@NamedQuery
@PersistenceContext
@Table
@Column
@Id
@Transient
@OneToOne
@OneToMany
... Any others that we need

So the idea is that I will perform a diagnostic checking first for the jakarta.persistence.* import. But if that is not present then I will search more granularly for annotation specific imports.

Once we have decided if these are worth doing then I can open up more detailed issues individually.

This problem would be solved using the current framework of building a jakarta persistence collector in the language server that tests for all of these annotations

Technically for coverage I can perform this for every single annotation in the spec, at section 11 of the spec. Would eclipse be able to tell from which package this annotation is coming from? If not I can implement all of the annotations with their respective import packages required

[kathrynkodama]

I don't think it's necessary that we implement our own diagnostics for correcting the imports as the Java Language Server already offers this capability