Cache test requirements in GitHub actions

Currently we install them with tox, which is not cached, and appears to take >1 min of the test time. Should we see if caching could reduce it?

One option is to cache .tox -- e.g. https://github.com/lsst-sqre/safir/issues/2

Another is probably to move off tox. (Per About caching workflow dependencies, GitHub workflows would cache dependencies with minimal configuration effort.)

If we called pip directly rather than isolating in tox, something like this could work:

- uses: actions/setup-python@v4
  with:
    ...
    cache: 'pip'
    cache-dependency-path: |
      mypy-requirements.txt
      build-requirements.txt
      test-requirements*.txt

Note that I'm not actively pitching to reduce reliance on tox, merely bringing it up as a possibility.

Inizia esaminando i workflow di GitHub Actions e la configurazione di tox, insieme a mypy-requirements.txt, build-requirements.txt e test-requirements*.txt. Confronta il caching di .tox con l'opzione di cache pip di setup-python. Il lavoro è completato quando l'approccio scelto riduce l'installazione ripetuta delle dipendenze di test e il workflow di test continua a superare i test.