Start outputting tags

So far the Java analyzer only provides automated feedback on submitted solutions, but [analyzers can also tag them](https://exercism.org/docs/building/tooling/analyzers/tags).

There are multiple approaches to implement this:

- We can start outputting tags in the exercise-specific analyzers, and exercises for which no analyzer is implemented yet will receive no tags on their submissions.
- We can implement a 'global' analyzer that is able to identify paradigms, techniques, constructs etc regardless of which exercise a solution belongs to, so that _all_ submissions will receive tags.
- We can combine both options of course.

I found that the [C# Analyzer took the second option](https://github.com/exercism/csharp-analyzer/blob/main/src/Exercism.Analyzers.CSharp/Analyzers/TagAnalyzer.cs). This makes sense, since a large portion of the tags currently implemented are exercise-agnostic. Perhaps it can serve as a good example to get started.

Inizia leggendo la documentazione sul tagging dell'analyzer collegata nell'issue, poi confronta gli approcci proposti con l'esempio C# in src/Exercism.Analyzers.CSharp/Analyzers/TagAnalyzer.cs. L'issue non identifica entry point Java, test o un piano di implementazione definito; il lavoro sarebbe completato quando sarà concordato un approccio al tagging e verranno emessi tag per le submission Java.

Scritto dal modello di indicizzazione a partire dal testo della issue.