Release kedro-datasets 2.0.0

[merelcht]

To do/check

• Are all mentions of DataSet gone?: chore: Clean up code for old dataset syntax compatibility #465
• Do all datasets have the keyword marker * in the __init__ methods added in feat(datasets): make datasets arguments keywords only #358?: chore: Update datasets to be arguments keyword only #466
• Finish and merge build(datasets): upgrade s3fs to newer calver #348 -> build(datasets): Bump s3fs #463
• Nice to have: Make sure all example code blocks for datasets are runnable#2287

[astrojuanlu]

If we're not in a hurry could we do #313 ? Or maybe too disruptive? (We can wait to 3.0)

[Galileo-Galilei]

I think 2.0.0 is also a good time to do #353, but there were concerns that it could affect kedro-viz. Should we move on this one?

[noklam]

#313 I don't think we need to rush for that, it's slightly untidy for us to keep setup.py but it is not that bad.
#353 I tend to agree with the rename, though it may be too disruptive. Would it be too bad if we rename but keep an alias for MatplotlibWriter, and in docs we use MatplotlibDataset and keep a small note that it is aliased MatplotlibWriter?

[astrojuanlu]

#313 I don't think we need to rush for that, it's slightly untidy for us to keep setup.py but it is not that bad.

#313 (comment)