Bump kedro-datasets to 2.0.0

[merelcht]

Description

Bump kedro-datasets to the latest 2.0.0 release.

Development notes

Developer Certificate of Origin

We need all contributions to comply with the Developer Certificate of Origin (DCO). All commits must be signed off by including a Signed-off-by line in the commit message. See our wiki for guidance.

If your PR is blocked due to unsigned commits, then you must follow the instructions under "Rebase the branch" on the GitHub Checks page for your PR. This will retroactively add the sign-off to all unsigned commits and allow the DCO check to pass.

Checklist

• Read the contributing guidelines
• Signed off each commit with a Developer Certificate of Origin (DCO)
• Opened this PR as a 'Draft Pull Request' if it is work-in-progress
• Updated the documentation to reflect the code changes
• Added a description of this change in the RELEASE.md file
• Added tests to cover my changes
• Checked if this change will affect Kedro-Viz, and if so, communicated that with the Viz team

[astrojuanlu]

kedro/pyproject.toml

Line 82 in 1cd7d61

"s3fs>=0.3.0, <0.5", # Needs to be at least 0.3.0 to make use of `cachable` attribute on S3FileSystem.

Guessing that we can remove s3fs from our test requirements?

[merelcht]

kedro/pyproject.toml

Line 82 in 1cd7d61

"s3fs>=0.3.0, <0.5", # Needs to be at least 0.3.0 to make use of `cachable` attribute on S3FileSystem.

Guessing that we can remove s3fs from our test requirements?

No this is needed for testing cloud interactions via fsspec.

It looks like the docs are still the issue...

[astrojuanlu]

It's because of conflicting dependencies. However, maybe we don't need kedro-datasets anymore to build the docs...!

[astrojuanlu]

✔️

[astrojuanlu]

RTD build times cut in half ✌🏽