Remove a work-around needed during the transition away from Rails

In cb4696d (deploy: copy back a couple files to help transitioning
away from Rails, 2024-09-23), I added a work-around to help keep things
working while caches slowly drain and some readers invariably must have
been looking at content that had been served from the Rails app (and
linked to differently-named CSS files, for example).

The caches had ample opportunity to drain in the meantime, it's time to
pay down the technical debt and remove that work-around.

Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>

Author: dscho

.github/actions/deploy-to-github-pages/action.yml

@@ -85,25 +85,6 @@ runs:
       shell: bash
       run: npx -y pagefind@${{ env.PAGEFIND_VERSION }} --site public
 
-    - name: Temporarily copy some Rails assets to help the transition
-      shell: bash
-      run: |
-        # To help with the transition from the Rails app to the Hugo/Pagefind site, where
-        # at least for a while the cached version of git-scm.com might be served via
-        # Cloudflare, according to the first transition attempt on Sep 20, 2024, potentially
-        # partially, i.e. _some_ assets might still be cached, _some_ others might not, let's
-        # copy the most prominent assets to the new page so that, say, the original front page
-        # won't fail to load the style sheet and Javascript libraries that it needs.
-        set -x &&
-        mkdir -p public/assets &&
-        for f in application-93865c5c820c24f4c599e8b9c544bcd8a0d03260f9b16c9ba80b6a00082112c9.css \
-          application-f7a750114a26afea236a5cc26f6ff3925a14c5901e9ea9018fb869432d0cbee3.js \
-          modernize-b3ebe0c31c24f230dc62179d3e1030d2e57a53b1668d9382c0a27dbd44a94beb.js
-        do
-          curl -Lfo public/assets/$f https://git-scm.com/assets/$f ||
-          echo "::error::could not copy $f from https://git-scm.com/" >&2
-        done
-
     - name: upload GitHub Pages artifact
       uses: actions/upload-pages-artifact@v3
       with: