Avoid deprecation availability in types lint rule

[l-trotta]

As titled, also fixing the 2 errors it caught (which were redundant because the annotations were already correctly present at the field level)

[github-actions]

Following you can find the validation changes against the target branch for the API.

API	Status	Request	Response
esql.query	🔴	380/383 → 381/383	0/0

You can validate this API yourself by using the make validate target.

[flobernd]

Thank you!

What do think about making this more generic? Like maintaining a list of allowed tags per type in the metamodel (alias, interface, ..., property, enum-member, ..., request, ...).

The compiler already does these kind of checks internally, but it might be useful for minting as well.

We can do this in a follow up task, but we should chose a more generic name for the linter rule/check right from the start, if we want to go that route 🙂