Create issues for refactoring datasets

[lorenzo-cavazzi]

Go through the datasets code and:

• Identify the duplicated data from the KG/core APIs
• Chat with KG/python teams and agree on how to proceed here (hint: until we have a dataset service, we should probably fetch data from renku-core, and then fetch extra info from KG and enrich the UI. If KG is indexing, we should re-fetch KG info later; if it's not indexed, we should show a prominent warning pushing the user to index the project. Making it a 2 steps approach, core first then KG, would simplify the logic too)
• Define a clear strategy for the components and add detailed info to the issues. That should include how to tackle tasks like removing the form generator (hint: this might involve using notifications coming from the UI server fed by our brand new RabbitMQ 🐰 )
• Dataset UI components should manage their own redux state. Currently, they rely on Project to do this (see Project.js>mapStateToProps and >subComponents -- this code can be cleaned up and moved to the dataset component)

[lorenzo-cavazzi]

Here is the follow-up issue with detailed information.

#2415

No changes to the current KG/core implementations needed.