feat: add package.json options to Related

[agilgur5]

Summary

New features like customConditions, resolvePackageJsonExports, and resolvePackageJsonImports are Related to moduleResolution

Details

• these influence how moduleResolution works, and so should be Related to it
  • and mention moduleResolution in their description as well (see also feat: link to moduleResolution from exports configs #2891)
• and also Related to each other

[agilgur5]

Alright think this is my last PR for the time being 😅

[jakebailey]

Hm, by this argument, I'm pretty sure there are loads of other options that affect module resolution, like suffixes, paths, json modules, etc; where do we draw the line?

[agilgur5]

It's a good question, I thought about that too. I'm not opposed to adding more relatedTo actually.
These 3 just are particularly relevant in the node16+ world.

I actually didn't know these options existed -- and thought that changing moduleResolution was the only way to get these to work (one of the reasons why we prioritized ezolenko/rollup-plugin-typescript2#453) -- until I read through the reference more recently.

In a similar line of thought, could argue that these 3 specifically are impacted by moduleResolution's setting, whereas the others are not necessarily impacted (or not so directly).
Again though, I'd be fine adding more relatedTo because they are all relevant for different use cases; node16+ is just more relevant to a wide audience (the vast majority of TS users, I would guess) and is timely right now

[andrewbranch]

I think the completeness of these lists is bound to be a little arbitrary, but I like the idea of increasing the discoverability of these lesser-known related options. I’ve added my own suggestions to the list, as well as some to module.