Trigger CI to publish pending version bump

[MarcAstr0]

Summary

• The @azure/identity security bump (PR Bump @azure/identity to ~4.13.0 (security fix) #1600) was never published to npm because the publish workflow had broken OIDC auth at the time (PR OIDC integration enabled #1596)
• The workflow was fixed in PR Disable OIDC #1601, but that commit only touched .github/** (which is in paths-ignore), so no publish run was triggered
• This cosmetic whitespace change triggers a new publish run to pick up the pending changeset and bump all lockstep packages from 4.0.1 → 4.0.2

Test plan

• Verify the publish workflow triggers after merge
• Verify packages are published to npm with the new version

🤖 Generated with Claude Code

[github-actions]

Oops, looks like you forgot to add a changeset.

⚠️ Please run rush change and commit the changeset file.

This command will prompt you for a change description and generate a changeset file. You can read more about changesets here.

Remember that you should use the version bump that is appropriate for the change you are making:

Version bump	Meaning
patch	Bug fixes, documentation changes, etc.
minor	New features, non-breaking changes
major	Breaking changes

If you are unsure about which version bump to use, please ask in the comments and we will help you out.