Fix CI tests hang forever (sometimes)
# What does this PR do?

Set `--max-worker-restart=0` for `pytest` command in CircieCI workflow file.

Currently, the tests could hang forever if `--dist=loadfile` is specified, and when a worker is crashed, and we finally got `Too long with no output (exceeded 10m0s): context deadline exceeded`. For example, [this job run](https://app.circleci.com/pipelines/github/huggingface/transformers/41092/workflows/9d84d20f-be88-4a20-b17e-07d5437b59f9/jobs/467619).

## Remark:

 - I opened [an issue](https://github.com/pytest-dev/pytest-xdist/issues/784#issue-1252433606) in `pytest-xdist` repo. 
 - The reason that the worker crashed is still unclear yet. It might be related to [memory issue #17470](https://github.com/huggingface/transformers/pull/17470). But a general issue of memory leak in tests also exists.
_The documentation is not available anymore as the PR was closed or merged._<|||||>From the experimentation, with the argument `--max-worker-restart=0`:

- all tests passed before the worker crashed --> marked as passed
- the test where the worker crashes --> marked as failed
- all tests not yet run before the worker crashed -> won't be marked at all, neither as passed nor as failed (i.e. won't be sent to other workers)<|||||>> From the experimentation, with the argument `--max-worker-restart=0`:
> 
> * all tests passed before the worker crashed --> marked as passed
> * the test where the worker crashes --> marked as failed
> * all tests not yet run before the worker crashed -> won't be marked at all, neither as passed nor as failed (i.e. won't be sent to other workers)

I understand we might want to the tests to be run on other workers, but currently without  `--max-worker-restart=0`, the CI hangs forever (if a worker crashes), which is not good neither.<|||||>~~(BTW, it looks like this issue happens in docker, say `circleci/python:3.7`, but not on the GCP VM without docker)~~