chore: align release-please state with v3.0.1 tag

[nieblara]

Summary

Unsticks release-please after the immutable-releases fallout so we can cut v3.0.2 as the first real 3.x release.

• Bumps .release-please-manifest.json, package.json, and PROVENANCE.md from 3.0.0 to 3.0.1 so release-please's view of state matches the v3.0.1 git tag.
• Adds last-release-sha: ac751372919a03537b86daa867d3b88c81a6db02 (the v3.0.1 commit) to release-please-config.json so release-please only considers commits after v3.0.1 and doesn't walk all ~700 commits from the beginning of the repo.
• Uses a Release-As: 3.0.2 footer in the commit message so release-please proposes chore(main): release 3.0.2 on the next run (the only commits between v3.0.1 and HEAD are a ci: change from ci: implement immutable releases support with actions/attest #689 and this chore, neither of which triggers a bump on its own).

Context

• The release-please PR that bumped manifest to 3.0.0 (chore(main): release 3.0.0 #648) merged, but the v3.0.0 tag/release never got published due to immutable releases.
• v3.0.1 was hand-cut on commit ac75137 without a manifest update. Its GitHub release has zero assets (all prior manual-publish.yml runs failed on immutable releases), and npm is still at 2.2.0.
• With no v3.0.0 tag and no anchor, release-please walked the full repo history and opened chore(main): release 0.12.1 #690 proposing 0.12.1 (now closed).

Next steps after merge

1. release-please should open chore(main): release 3.0.2 as a draft-creating PR.
2. Merging that PR will exercise the new flow from ci: implement immutable releases support with actions/attest #689 end-to-end: draft release, gh release upload, actions/attest@v4 for binaries and images, then publish-release un-drafts.
3. Verify with gh attestation verify and npm view @launchdarkly/ldcli version.

Test plan

• Merge this PR.
• Confirm release-please opens chore(main): release 3.0.2 (not another 0.12.x).
• Merge the release-please PR and watch the workflow draft + attest + un-draft the release.
• Verify binary and image attestations with gh attestation verify.
• Verify npm view @launchdarkly/ldcli version returns 3.0.2.

Made with Cursor

---

Note

Low Risk
Release automation/config-only changes (version metadata and release-please anchoring) with no impact on runtime code paths.

Overview
Aligns release metadata to v3.0.1 by bumping the release-please manifest, package.json, and the version referenced in PROVENANCE.md from 3.0.0 to 3.0.1.

Updates release-please-config.json with last-release-sha to anchor future release-please runs at the v3.0.1 commit and avoid scanning the full repo history when generating the next release PR.

^{Reviewed by Cursor Bugbot for commit 0f8416f. Bugbot is set up for automated code reviews on this repo. Configure here.}