Imports and requires may not be using Node Loaders/Registration for ESM

The Yarn PNP mechanism uses loaders and/or registration for CJS and ESM support.

Presently using `-r .pnp.cjs` works appropriately in AWS SAM but using `--loader` runs into a host of issues as detailed in:

https://github.com/yarnpkg/berry/issues/6604

I'm not clear why the two are not working together, as they work in other contexts - but in the AWS SAM `index.mjs` it seems that the tryRequire path goes through a route where `pnp.setup();` is unable to monkey patch calls once it is working within the CJS loader by route of the ESM loader.

從 issue 中描述的 AWS SAM index.mjs 路徑開始，重點嘗試 tryRequire 和對 pnp.setup() 的呼叫，然後比較使用 -r .pnp.cjs 與 --loader 時的行為。查看連結的 Yarn issue，並重現 CJS 和 ESM 的情況；當 imports 和 requires 在 AWS SAM 與 Yarn PnP 下能夠協同運作時，即表示完成。

由索引模型根據 Issue 內容生成。