docs: sync standalone package release artifacts after failed publish commit

[Hotell]

Summary

Recovery sync for the standalone release run #28669548663 that published to npm but failed before pushing to main.

The run published:

• @fluentui/react-icons-atomic-webpack-loader@0.0.5 ✅ (on npm)
• @fluentui/react-icons-svg-sprite-subsetting-webpack-plugin@0.0.5 ✅ (on npm)

…but died at the Tag step (fatal: tag 'react-icons-file-type@0.0.1' already exists), which runs before git push. As a result the version bumps, changelogs, and lockfile update never landed on main, and no @0.0.5 tags exist upstream.

What this PR does

Re-applies the artifacts the failed run would have committed (mirrors #1133):

• react-icons-atomic-webpack-loader → 0.0.5 (package.json + CHANGELOG)
• react-icons-svg-sprite-subsetting-webpack-plugin → 0.0.5 (package.json + CHANGELOG)
• package-lock.json version refs

react-icons-file-type is intentionally untouched (already published + tagged at 0.0.1).

Follow-up

After merge, the @0.0.5 git tags will be created at the merge commit to realign tags ↔ npm ↔ disk. A separate change will make the publish workflow idempotent so a mid-run failure (existing tag / already-published version) can no longer abort the pipeline.

[github-actions]

📋 PR Validation Summary

Check the Build react library job summary for detailed reports:

• 📦 Bundle Size — size comparison against the base branch
• 📖 Docsite Preview — build artifact with local preview instructions

To view: click the link above → select the Build react library job → open the Summary tab.