chore: release packages

[Jane Chu (janechu)]

Pull Request

📖 Description

Version bump PR generated via npm run bump, consuming all pending beachball change files and releasing:

• @microsoft/fast-build@0.11.0 → 0.12.0 (minor) — adds the webui-framework-prerelease conversion target and the markers_v2 hydration marker option. Paired Rust crates microsoft-fast-build and microsoft-fast-convert are synced to 0.12.0 via the postbump hook.
• @microsoft/fast-element@3.0.4 → 3.1.0 (minor) — adds an opt-in markers_v2 export for FAST Element 2.x indexed hydration markers, plus a patch blocking iframe srcdoc attribute bindings in the default DOM policy.

Dependent workspaces (@microsoft/fast-router, @microsoft/fast-test-harness, example apps, sites/benchmarks, sites/website) have their @microsoft/fast-element/@microsoft/fast-build dependency ranges bumped to match; none of them required their own version bump.

No source code is changed in this PR — only package.json versions, CHANGELOG.md/CHANGELOG.json, paired Cargo.toml/Cargo.lock files, and package-lock.json, plus deletion of the consumed change/ files.

👩‍💻 Reviewer Notes

This PR was opened from a publish_<timestamp> branch by an admin, so npm run checkchange bypasses the change-file requirement per CONTRIBUTING.md > Manual version bumps. Please verify the diff is limited to version/changelog bookkeeping as described above.

📑 Test Plan

• npm run build — all packages build successfully.
• npm run test — all tests pass.
• npm run format:check — clean.
• npm run checkchange — bypassed as expected (branch matches publish_<timestamp>, actor has admin role).
• node build/scripts/create-github-releases.mjs --check-only — confirms @microsoft/fast-build@0.12.0 (+ crates) and @microsoft/fast-element@3.1.0 are the only workspaces needing a release.

✅ Checklist

General

• I have included a change request file using $ npm run change
• I have added tests for my changes.
• I have tested my changes.
• I have updated the project documentation to reflect my changes.
• I have read the CONTRIBUTING documentation and followed the standards for this project.

Agents

• I have linked to an existing issue in this project that this change addresses
• I have read the skills
• I have read the DESIGN.md file(s) in packages relevant to my changes
• I have updated the DESIGN.md file(s) in packages relevant to my changes

⏭ Next Steps

• After merge, the nightly cd-github-releases.yml workflow (or a manual gh workflow run cd-github-releases.yml) will create GitHub releases for the newly-tagged packages, and the following azure-pipelines-cd.yml run will publish them to npm/crates.io.