[ENH] Add pyarrow and s3fs

[viniciusdc]

Related to #1359

Changes introduced in this PR:

• Add two new packages to Dask env, pyarrow and s3fs

Types of changes

What types of changes does your PR introduce?

Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds a feature)
• Breaking change (fix or feature that would cause existing features not to work as expected)
• Documentation Update
• Code style update (formatting, renaming)
• Refactoring (no functional changes, no API changes)
• Build related changes
• Other (please describe):

Testing

Requires testing

• Yes
• No

In case you checked yes, did you write tests?

• Yes
• No

Documentation

Does your contribution include breaking changes or deprecations?
If so have you updated the documentation?

• Yes, docstrings
• Yes, main documentation
• Yes, deprecation notices

Further comments (optional)

If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered and more.

[iameskild]

Looks good to me :)

I wonder if it's also worth adding gcsfs, what do you think?

[viniciusdc]

Looks good to me :)

I wonder if it's also worth adding gcsfs, what do you think?

If we add s3sf I don't see a problem, though to be honest I would prefer to keep s3fs and gcsfs as something the user should add to a personal env based on filesystem/dask. The reason is, that dask should be the basic env for running dask operations, anything outside this should go to a user/group-based env.