Add @rushstack/storybook-telemetry-stub package

[Copilot]

• Rename folder from storybook/storybook-telemetry-stub to storybook/telemetry-stub and update rush.json
• Rename src/index.ts to src/storybook-telemetry-stub.ts
• Remove CHANGELOG.json and CHANGELOG.md
• Update package.json: version 0.0.0, remove exports field, update directory
• Fix sanitizeError to use generic type
• Rewrite tests: use import * as, remove local expected-export objects, use proper casting
• Run rush build -t repo-toolbox and update README
• Move @storybook/telemetry from browser-approved-packages.json to nonbrowser-approved-packages.json
• Use Object.entries in test loops instead of separate key lookup
• Build and test the package (all 8 tests pass)
• Run code review and CodeQL checks (no issues found)
• Add Rush change file for @rushstack/storybook-telemetry-stub
• Revert lockfiles to main and rerun rush update for minimal diff
• Remove @storybook/telemetry-7 dependency, hardcode v7 exports in test
• Rewrite README with better organization: problem, alternatives, how it works, usage
• Add clarity that this primarily targets old out-of-support versions (6 and 7)

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[dmichon-msft]

@copilot Since this is adding a new project, you will also need to update the readme:

rush build -t repo-toolbox
node repo-scripts/repo-toolbox/lib-commonjs/start.js readme

Commit the modified repo readme.

[Copilot]

@copilot Since this is adding a new project, you will also need to update the readme:

rush build -t repo-toolbox...

Built repo-toolbox and updated README.md in 4e51f83.

[dmichon-msft]

@copilot needs a standard Rush change file (i.e. the one produced by rush change --no-fetch).

[Copilot]

@copilot needs a standard Rush change file (i.e. the one produced by rush change --no-fetch).

Added the Rush change file in 7501910.

[dmichon-msft]

@copilot The build is failing because the lockfiles contain a ton of unrelated version bumps. Revert the lockfiles to the version in main, then rerun rush update. We should expect to see the only changes be related to the newly added package.

[Copilot]

@copilot The build is failing because the lockfiles contain a ton of unrelated version bumps. Revert the lockfiles to the version in main, then rerun rush update. We should expect to...

Reverted both lockfiles to main and reran rush update in 4150f44. The default lockfile diff is now limited to the new package's dependencies, and the build-tests lockfile has no changes.

[dmichon-msft]

@copilot Since storybook 6 and 7 are officially out of support, go ahead and just hardcode the expected types for them instead of actually installing the corresponding @storybook/telemetry package version. Be sure to reset the lockfiles to the version from origin/main and regenerate them with rush update after removing the dependency.

[Copilot]

@copilot Since storybook 6 and 7 are officially out of support, go ahead and just hardcode the expected types for them instead of actually installing the corresponding @storybook/telem...

Removed the @storybook/telemetry-7 devDependency and hardcoded the expected v7 exports (verified against @storybook/telemetry@7.6.24) in the test. Also removed @storybook/telemetry and @storybook/telemetry-7 from approved packages, reset lockfiles to origin/main, and regenerated with rush update. The lockfile diff is now minimal (58 lines, only the new package's v8 dependency). All 8 tests pass in 46ac29c.

[octogonz]

This README is important, since the usage and underlying motivations are not obvious from looking at the package itself. I think the README can be organized a bit better, along the lines of:

1. The problem: Storybook makes network calls (why), mutates package.json (how? why?) during normal operation, etc. These are really separate behaviors, so let's call them out individually rather than rolling them into one sentence.
2. Alternatives: Do certain versions of Storybook support environment variables or "off" switches? People from the Storybook community may claim that this stub is not needed for whatever reason, but maybe they are wrong in some edge cases. The README can provide a paragraph that we can use to track those details.
3. How does it work: Explain stubbing.
4. How do you use it? Briefly explain how somebody enables this in their Rush repo.

[octogonz]

Approved with comments

[dmichon-msft]

@copilot Add clarity that this is really targeting old, out-of-support versions (6 and 7 mostly). Newer versions have more complete support for disabling the telemetry layer and not writing the root package.json.

[dmichon-msft]

Abandoning this for now in favor of setting the right environment variables when invoking Storybook.