Make the link to different object types explicit for the docs

[ksimpson-work]

Make the object links in the docs point somewhere

• quickly made this change in passing as I was working on adding documentation for core.experimental.system (which as a singleton instance, should certainly have a link to the System class in my opinion)

built the docs locally and was able to click my way around the objects as expected

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[ksimpson-work]

/ok to test

[leofang]

Thanks for catching all the missing hyperlinks, Keenan. I have one question: Is it possible for us to keep it short? Maybe we can change all the ::currentmodule entries? (not sure)

The long names (I see your already added ~ so after rendering they are still short) have two issues

1. it's harder to write
2. by the time we move all objects to out of the experimental module, we'd have to check all docstrings again

[ksimpson-work]

that was a perfect solution

[ksimpson-work]

/ok to test

[ksimpson-work]

/ok to test

[ksimpson-work]

/ok to test

[leofang]

I thought this does not need to be changed?

[ksimpson-work]

you are correct, the issue was actually a missing pip install. fixed

[vzhurba01]

LGTM but I see Leo has a final question pending

[ksimpson-work]

links for ContextOptions are not working because ContextOptions is TODO and not imported. Context is not import in init and is also not linking. Do we want this behaviour, or do we want Context to link?

[leofang]

No need to sweat for Context (and MemoryResource too, I guess) for now as they aren't really fully public.