feat(build): migrate to esm from cjs BREAKING_CHANGE

[aorinevo]

Changes

BREAKING_CHANGE: This PR migrates Shepherd codebase to ESM from CJS.

Benefits

• Enables us to finally upgrade to latest Ora, Chalk, and log-symbols.
• Closes Add support for esm modules #607

Highlights

• ESM requires import paths to end in an extension, hence why .js is added. Note, using .ts extension is an option but in compiling the code, the import paths are not updated to .js which is an issue.
• Update Ora, Chalk, and log-symbols to latest.
• __dirname and __filename variables are available in CommonJS but not ESM environments and requires a bit more work to get these values. See, for example: https://github.com/NerdWalletOSS/shepherd/pull/690/files#diff-f89d0ffd37a33ca099d3286296b3159bd3c8faa06c9f22fd88733902bf89b437R6-R7
• Destructuring directly off of a CommonJS export results in a TS error. To work around this, use the default export and destructure off the default. See, for example: https://github.com/NerdWalletOSS/shepherd/pull/690/files#diff-c345dd7546bef3e0855e7a13ee7c0e0ef28b56ddca5dd9177750c5ad55d038a9R2-R4

Todo

1. Fix Jest runner: import paths do not resolve due to use of .js extension vs .ts.
2. Drop support for Node <= 18.
3. Fix workflow (e.g., linting step).

Local Test Screenshots

[aorinevo]

Not sure why, but the linting step, while successful, ultimately gets canceled (see screenshot).

[aorinevo]

Issue is likely due to the fact that node.matrix contained Node v22 which hasn't been released yet.

[aorinevo]

Close in favor of #846