CI/TST: Use CI moto service instead of subprocess
- [x] tests added / passed
- [x] Ensure all linting tests pass, see [here](https://pandas.pydata.org/pandas-docs/dev/development/contributing_codebase.html#pre-commit) for how to run them


@lithomas1 how feasible do you think it would be to move our Windows and MacOS builds to Github Actions given the current jobs there?

For Azure Windows, appears we can't use Linux containers
https://stackoverflow.com/a/55351920
https://stackoverflow.com/a/57751095

For Azure MacOS, appears it doesn't support containers in general
https://docs.microsoft.com/en-us/azure/devops/pipelines/process/service-containers?view=azure-devops&tabs=yaml#requirements


The goal here was to hopefully avoid flaky behavior of running a moto service in a subprocess by running it in a container instead.
 Darn. For Github Actions, it looks like service containers only work for Ubuntu runners :(

https://docs.github.com/en/actions/using-containerized-services/about-service-containers#about-service-containers @jreback thoughts about only running these s3 tests only in Linux Python 38 & 39 (and the Linux db build)? Before it was running in the Windows Python 38 & 39 builds and the Linux db build 

One can still run this locally on Windows or Mac with the subprocesses > @jreback thoughts about only running these s3 tests only in Linux Python 38 & 39 (and the Linux db build)? Before it was running in the Windows Python 38 & 39 builds and the Linux db build
> 
> One can still run this locally on Windows or Mac with the subprocesses

sounds ok to me ping when ready here Ready and all green here.  @lithomas1 if any comments can you merge master thanks @mroeschke  18 failed tests when running tests locally on ubuntu with `aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host localhost:5000 ssl:default [Connect call failed ('127.0.0.1', 5000)]`

Is there something that needs to now be changed in the local dev setup also or should these tests be skipped locally?
 on WSL 44 failed.