CI: docker 32-bit linux build #32709
- [x] closes #32709


Thanks @VirosaLi. Are you able to integrate this into our existing setup at all? See how we handle the Python 3.9 build (e.g. https://github.com/pandas-dev/pandas/blob/master/ci/setup_env.sh#L3-L6 and elsewhere). This pull request is stale because it has been open for thirty days with no activity. Please update or respond to this comment if you're still interested in working on this. @fangchenli can you update this. would be great to get this to work (xfailing the tests as needed of course). W/o this or similar we are going to have a very hard time continuing to support 32-bit. Windows py38_np18 had stalled. restarted.

the following tests are failing on the 32bit wheel builds

```

=========================== short test summary info ===========================
FAILED test_venv/lib/site-packages/pandas/tests/groupby/test_groupby.py::test_groupby_nat_exclude
FAILED test_venv/lib/site-packages/pandas/tests/io/formats/test_info.py::test_info_int_columns
FAILED test_venv/lib/site-packages/pandas/tests/window/test_grouper.py::TestGrouperGrouping::test_groupby_rolling_string_index
FAILED test_venv/lib/site-packages/pandas/tests/window/test_grouper.py::TestGrouperGrouping::test_groupby_rolling_no_sort
= 4 failed, 64345 passed, 7420 skipped, 1047 xfailed, 6 xpassed, 14 warnings in 932.75s (0:15:32) =
```

so will want to merge some of the changes here into 1.1.x.

@jreback could wait till this is approved and merged and do a partial backport or open a separate PR now directly against 1.1.x with the changes to those tests here. thanks a lot @fangchenli this is great @simonjayhawkins pls backport what u need against 1.1.x @meeseeksdev backport 1.1.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.1.x
$ git pull
```

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

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

```
$ git commit -am 'Backport PR #35898: CI: docker 32-bit linux build #32709'
```

4. Push to a named branch :

```
git push YOURFORK 1.1.x:auto-backport-of-pr-35898-on-1.1.x
```

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

> "Backport PR #35898 on branch 1.1.x"

And apply the correct labels and milestones.

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

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