doc: reorganize docs of module hooks and mark sync hooks as release candidate

[joyeecheung]

doc: mark sync module hooks as release candidate

doc: reorganize docs of module customization hooks

This reorganizes the documentation of module customization hooks
to promote the synchronous variant as it has fewer caveats.
Previously the documentation was organized as follows:

To do something:

1. For asynchronous hooks, do this, which may have these caveats
2. For synchronous hooks, do this, which does not have the caveats

To do something else:

1. For asynchronous hooks, do this, which may have these caveats
2. For synchronous hooks, do this, which does not have the caveats

It's now organized as follows:

Synchronous hooks:

• To do something, do this.
• To do something else, do this.
  (No mention that it doesn't have caveats, because users are not supposed
  to burden themselves with caveats in the other API that they do not
  use).

Asynchronous hooks:
They have these caveats, if they are too complex to deal with, consider
use the synchronous variant.

• To do something, do this, which may have these caveats.
• To do something, do this, which may have these caveats.

Refs: #56241

[nodejs-github-bot]

Review requested:

• @nodejs/loaders

[GeoffreyBooth]

Suggestions. Thank you for doing this.

[joyeecheung]

Rebased to resolve the conflicts and addressed reviews. PTAL, thanks @GeoffreyBooth

[GeoffreyBooth]

Suggested change

	The asynchronous customization hooks have many caveats and the it is uncertain if their
	The asynchronous customization hooks have many caveats and it is uncertain if their

[aduh95]

Suggested change

	Alternatively, `registerHooks()` can be called from the entry point.
	Alternatively, `registerHooks()` can be called from the entry point.

[aduh95]

Suggested change

	last-in, first out (LIFO). If both `hook1` and `hook2` define a `resolve`
	last-in, first-out (LIFO). If both `hook1` and `hook2` define a `resolve`

[aduh95]

Suggested change

	<!-- lint disable prohibited-strings remark-lint-->
	Node.js' default ← `hook1.resolve` ← `hook2.resolve`
	<!--lint enable prohibited-strings-->
	Node.js default `resolve` ← `hook1.resolve` ← `hook2.resolve`

[GeoffreyBooth]

And the other similar case later on.