Improve Error Messages when Access Client References

[sebmarkbage]

This renames Module References to Client References, since they are in the server->client direction.

I also changed the Proxies exposed from the node-register loader to provide better error messages. Ideally, some of this should be replicated in the ESM loader too but neither are the source of truth. We'll replicate this in the static form in the Next.js loaders. cc @huozhi @shuding

• All references are now functions so that when you call them on the server, we can yield a better error message.
• References that are themselves already referring to an export name are now proxies that error when you dot into them.
• use(...) can now be used on a client reference to unwrap it server side and then pass a reference to the awaited value.

[gnoff]

nit: "from the server" is ambiguous since SSR is on the server and the function can be called there. Can we make this error message reinforce the terminology that more clearly delineates between RSC and SSR/Client instead of server vs client?

[sebmarkbage]

Yea we probably need to think through our messaging here. Right now it's that SSR is an "emulated client" and not a server.

[huozhi]

Suggested change

	`Attempted to call the default export of ${moduleId} from the server` +
	`Attempted to call the default export of ${moduleId} from the server ` +

[huozhi]

Suggested change

	`the server, it can only be rendered as a Component or passed to props of a` +
	`the server, it can only be rendered as a Component or passed to props of a ` +