epic: First Release Cockpit

This is an umbrella issue preparing the cockpit for the first release.

• Finalise File Browser
• Finalise Dashboard
• Open Source the project
• Documentation
• Integrating it into the SDP release cycle
• Testing
• Integrate into a demo

Storage Browser

There are multiple open PRs which need to be reviewed:

• https://github.com/stackabletech/cockpit/pull/208
• https://github.com/stackabletech/cockpit/pull/289

Dashboard

• https://github.com/stackabletech/cockpit/pull/293
• https://github.com/stackabletech/cockpit/pull/278

Open Source the project

• https://github.com/stackabletech/cockpit/pull/204
• Decide whether we want to rewrite history or not
• Analyse/Run a cleanup of commits etc. -> to make sure we never reference customers
• Flip the switch

Documentation

I believe today we have no documentation in our main docs telling anyone about this project.
We'll need to change that.

• Include the Cockpit in our documentation

Integrating Cockpit into the SDP release cycle

Our release for each SDP version has a lot of steps and templates.
We need to make sure to include the Cockpit in this process going forward.

Testing

We need to do a lot of manual testing to see if everything is coherent.
For that, we might want to create a branch to work off and stabilise so that new features can be developed independently.

Integrate into demos

We want to showcase the cockpit, for that we should integrate it into one or more demos.
We need to decide whether we want to do that with something we call experimental and I'd also like us to talk about the screenshots. I expect the cockpit to develop faster than most other tools we have in our stack and I hate that we have to manually update the screenshots all the time.