Find source-map-support usages that need manual migration

Marks every source-map-support usage the automated migration leaves in place — an install() or register entry point that would only map part of the process, options Node has no equivalent for (retrieveSourceMap, retrieveFile, environment: 'browser') and the API beyond install (wrapCallSite, mapSourcePosition, ...) where no replacement could be written, bundler banner strings, package.json scripts whose command doesn't take Node's flags, type imports, re-exports, dynamic imports and test mocks — and records each with a suggested replacement in the SourceMapSupportManualMigrationSteps data table.