feat(node): Add a function to resolve entry point type

[timfish]

/**
 * Gets the current entry point type.
 *
 * `app` means this function was most likely called via the app entry point.
 * `import` means this function was most likely called from an --import cli arg.
 * `require` means this function was most likely called from a --require cli arg.
 * `unknown` means we couldn't determine for sure.
 */
export function getEntryPointType(): 'import' | 'require' | 'app' | 'unknown' {

Can be used to:

• Help add deprecation warnings when users aren't using --import [v9] Change default of onlyIncludeInstrumentedModules in Node SDK #14332
• Warn users who init Sentry via --require and later use ESM that instrumentation wont work

The code makes a point of returning unknown rather than giving false positives. For example, it returns unknown in these cases:

• Users pass paths to the Node CLI without file extensions
• There are filenames in the stack trace that match both the app entry point and --import/--require

[timfish]

I wanted to use string.matchAll and it turns out everything in es2020.string is fully supported by all the Node versions we support.

[codecov]

❌ 1 Tests Failed:

Tests completed	Failed	Passed	Skipped
205	1	204	9

View the top 1 failed tests by shortest run time

client-app-routing-instrumentation.test.ts Creates a navigation transaction for app router routes

Stack Traces | 30s run time

client-app-routing-instrumentation.test.ts:19:5 Creates a navigation transaction for app router routes

To view more test analytics, go to the Test Analytics Dashboard
Got feedback? Let us know on Github

[mydea]

Looks good to me!