integrate name resolution of rascal type-checker into Rascal code examples

[jurgenvinju]

I don't know how to add links to the docusaurus code blocks, or if this could work at all from the client side, but it would be great if we could feed the resolution of names of the type-checker into the documentation generator. That way people could browse in the documented APIs like they can with some Github source code viewers.

• This would take more computation time, so it could be an optional feature for the final publishing stage instead of during a preview.
• Reuse type-checker code from rascal-core which also uses timestamps for incrementalization
• Extracting the right def-use information from .tpl files is already done; this is a basic IDE construction feature we use in VScode and Eclipse
• What happens on the client side with multiple, non-unitary, link targets?

This sounds like a team effort @PaulKlint @JJWTimmer. Maybe we could have a call/meeting sometime in Feb?