chore: anchor release-please to this release cycle's base

last-release-sha records the merge parent so the squash merge itself lands the next cycle's boundary on main: version tags live on packaged children that are not on main, so release-please cannot find the boundary by tag. A release-as pin this PR's own version proves spent is retired by the same commit, so the merge cannot land a pin that would park the pipeline.

Author: settings-as-code-release

release-please-config.json

@@ -3,12 +3,11 @@
   "bump-minor-pre-major": true,
   "bump-patch-for-minor-pre-major": true,
   "include-component-in-tag": false,
-  "last-release-sha": "046adf3b24454f26f569850630809bcf481f8b84",
+  "last-release-sha": "76d33c84c47d5b9a2ae01f6e8a3f2a43538e2c73",
   "packages": {
     ".": {
       "release-type": "simple",
       "initial-version": "1.0.0",
-      "release-as": "2.0.1",
       "draft": true,
       "force-tag-creation": false,
       "extra-files": [