Add early support for `torchdata.stateful_dataloader.StatefulDataLoader` within the `Accelerator`

[byi8220]

What does this PR do?

Fixes https://github.com/huggingface/accelerate/issues/2859

This PR does the following:

1. Added a new field use_stateful_dataloader in DataLoaderConfiguration. Passing this into the config makes it so that all DataLoaders prepared and returned by the Accelerator are StatefulDataLoader objects from the torchdata library
2. Create a class DataLoaderAdapter which can wrap around and act as either PyTorch's DataLoader, or other variants of it such as StatefulDataLoader
3. Refactor DataLoaderShard, DataLoaderDispatcher, and SkipDataLoader to inherit from DataLoaderAdapter instead of DataLoader

Testing

Added new unit tests to test that StatefulDataLoader can be dropped in and loaded and saved from.

Caveats

• This PR does not pass the current test suite if the torchdata package is installed. The package itself may have conflicts with accelerate, see https://github.com/huggingface/accelerate/issues/2894
  • Running python -m pytest -sv ./tests with nightly torchdata installed does not pass all tests, output is actually 1 failed, 245 passed, 109 skipped, 27 warnings
  • However, if torchdata is not installed, all existing tests pass, suggesting this is not regressive.
• torchdata.stateful_dataloader.StatefulDataLoader is only available in the beta build of torchdata, this is not a stable feature.
• Adding another dependency (on a nightly package) means that almost none of the tests added in this PR is done underneath the existing images or imports.
• This has only been tested on my local workstation using a single GPU.
• The implementation of DataLoaderAdapter is somewhat invasive and uses some questionable reflection

Before submitting

• [ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
• [X] Did you read the contributor guideline, Pull Request section?
• [X] Was this discussed/approved via a Github issue (see above)
• [ ] Did you make sure to update the documentation with your changes? Here are the documentation guidelines, and here are tips on formatting docstrings.
• [X] Did you write any new necessary tests?

Who can review?

Anyone in the community is free to review the PR once the tests have passed. Feel free to tag members/contributors who may be interested in your PR.

@muellerzr

[HuggingFaceDocBuilderDev]

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.