Optimize Release Squash using Git Plumbing

To resolve persistent merge conflicts during the "Squash to Main" phase of the release workflow, we will replace the high-level git merge strategy with low-level git plumbing commands.

Problem: Massive refactorings and file moves without git mv cause Git's rename detection to fail during git merge --squash, leading to extensive conflicts that require "accept theirs" resolution.

Solution: Implement the "No-Checkout Snapshot" strategy in buildScripts/publishRelease.mjs. Instead of merging, we will construct a new commit on main that points directly to dev's file tree.

Plan: Update buildScripts/publishRelease.mjs to:

1. Fetch origin/main to get the latest parent hash.
2. Get the tree hash of the current dev HEAD (git rev-parse HEAD^{tree}).
3. Use git commit-tree to create a new commit object:
   • Tree: dev's tree
   • Parent: origin/main
   • Message: "vX.Y.Z"
4. Update the local main ref to this new commit (git update-ref).
5. Push the new commit to origin/main.

Benefits:

• Zero Conflicts: Bypasses conflict detection entirely.
• Performance: Instant execution (no file I/O or checkout).
• Reliability: Guarantees main is a byte-for-byte copy of dev.