CI: Debug min build timing out
I've gathered that it's due to some S3 test and that now is the time to enforce running non-single tests with xdist and `-n auto`.

Will follow up with one single build after: https://github.com/pandas-dev/pandas/issues/44584
@jbrockmendel this PR will "solve" the min build issue if you think it's good to go > Will follow up with one single build after: #44584

IIUC this means the marked tests won't be run at all on the CI until #44584? > > Will follow up with one single build after: #44584
> 
> IIUC this means the marked tests won't be run at all on the CI until #44584?

Correct. If you feel more comfortable for me to add the single build in this PR I can. > Correct. If you feel more comfortable for me to add the single build in this PR I can.

No, I'm fine with having it as a follow-up. Merging to get to green, can follow up if needed @meeseeksdev backport 1.4.x Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -m1 3d4ba05e9eec600375f85c4f2454e502f8f46bdd
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #45946: CI: Debug min build timing out'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45946-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #45946 on branch 1.4.x (CI: Debug min build timing out)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                 Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

```
git checkout 1.4.x
git pull
```

2. Cherry pick the first parent branch of the this PR on top of the older branch:
```
git cherry-pick -m1 3d4ba05e9eec600375f85c4f2454e502f8f46bdd
```

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

```
git commit -am 'Backport PR #45946: CI: Debug min build timing out'
```

4. Push to a named branch:

```
git push YOURFORK 1.4.x:auto-backport-of-pr-45946-on-1.4.x
```

5. Create a PR against branch 1.4.x, I would have named this PR:

> "Backport PR #45946 on branch 1.4.x (CI: Debug min build timing out)"

And apply the correct labels and milestones.

Congratulations — you did some good work! Hopefully your backport PR will be tested by the continuous integration and merged soon!

Remember to remove the `Still Needs Manual Backport` label once the PR gets merged.

If these instructions are inaccurate, feel free to [suggest an improvement](https://github.com/MeeseeksBox/MeeseeksDev).
                