WIP: Remove force push to Pantheon by preparing local history

[stevector]

This pull request removes the Git force push behavior.

• To do that it adds the --no-git-force to the invocation of terminus -n build:env:create.
• Making that change work, without breaking the push requires that the Git history in the CI container include the Git history present on Pantheon.
• That change to prepare the local CI Git History is accomplished with scripts/prepare-repo.sh
• To increase the confidence in that script, I've included some bats tests that create mock repos representing GitHub, the GitHub Actions Container, and Pantheon.

Here are site that consume this action that are working with this change:

• Remove force pushing fauxalgore/algore.website#20
• https://github.com/stevector/stevector-composed/pull/161

Before merging this PR, someone else should check that it works on their own consuming repo.

[stevector-streaming]

Don't merge this PR until figuring out if #46 is working

[stevector]

Thanks @stevector-streaming. Yes, I had to correctly require the branch before Composer / the Terminus plugin manager would use the 3.x branch of Build Tools. That seems to be working now after 571f74f

This build on the main branch of our personal site did not include the --force flag on the git push. https://github.com/stevector/stevector-composed/actions/runs/14457587267/job/40543999158

[stevector-streaming]

Thanks @stevector for figuring out the issue with #46.

[stevector]

I saw yesterday that Miriam's sample repo does use force pushing still. That reduces the urgency for me to get force pushing out. Also, I'm finding that getting it out in a way that accommodates all the permutations of repo patterns is even trickier than I anticipated (and I was expecting it to be tricky). I'd like to defer this work until we have a more coherent plan for the future of Build Tools.

[jazzsequence]

Setting back to Draft based on the last comment and failing deployments.