Generate classpath entries for FQN references

[timtebeek]

What's changed?

Right now fully qualified references do not generate classpath entries on the JavaTemplate classes, since we only loop over imports to generate those. We expand that to include any type use of classes that need imports.

What's your motivation?

When we want to swap between similar classes we would want to use FQNs in the recipes for readability.

Any additional context

• Plexus FileUtils refaster template recipes rewrite-migrate-java#272
• Call ShortenFullyQualifiedTypeReferences after visit #18

[knutwannheden]

I think I saw that this also covers annotations, which is good. I suspect that we will at some point also have to traverse the indirectly referenced types (supertypes, return types, parameter types, etc.), but let's leave it at this for now.

[timtebeek]

I think I saw that this also covers annotations, which is good. I suspect that we will at some point also have to traverse the indirectly referenced types (supertypes, return types, parameter types, etc.), but let's leave it at this for now.

Thanks for the quick review! Indeed I think we can iterate on this still, but since it's functional we can continue the work in those linked PRs and see what else pops up.