Fix publish-docs workflow to prevent over size limit atomvm_www Production branch

The "Production" branch of atomvm_www where www.atomvm.net is serverd via GitHub Pages can grow
incredibly large over time and exced the 1 GB size limmit for a "Pages" branch on GitHub.

This changes the workflow resets the branch to HEAD before commiting the new changes. All of the
intermediary changes are not useful for this branch, those changes are tracked in the code that
generates this content. We just want the one pevious commit as a fallback in the unlikely event a
publication goes terribly wrong and the documentation buils system is broken and unable to push
corrected changes.

Signed-off-by: Winford <[email protected]>

Author: UncleGrumpy

.github/workflows/publish-docs.yaml

@@ -119,12 +119,14 @@ jobs:
           cp -av html "/__w/AtomVM/AtomVM/www/doc/${{ github.ref_name }}"
       - name: Commit files
         id: commit_files
-        if: github.repository == 'atomvm/AtomVM'
+        # if: github.repository == 'atomvm/AtomVM'
         working-directory: /home/runner/work/AtomVM/AtomVM/www
         run: |
           git config --local user.email "[email protected]"
           git config --local user.name "AtomVM Doc Bot"
           ls -la doc/
+          git reset $(git commit-tree "HEAD^{tree}" -m "Live Production fallback")
+          git log
           git status "doc/${{ github.ref_name }}"
           git add "doc/${{ github.ref_name }}"
           git add .