ci(rocks): tracker to tackle issues we bump on often across our rocks repos

Why it needs to get done

There are different issues we bump on with our rocks CI. This will act as a parent issue for everything that we need to fix in order to allow us to tackle those in an organized and focused way.

We need this order to eliminate issues in our rocks CI and construct a more hassle-free developer experience.

What needs to get done

Tackle all issues below:

Quick tasks:

https://github.com/canonical/bundle-kubeflow/issues/797
https://github.com/canonical/charmed-kubeflow-workflows/issues/47
https://github.com/canonical/charmed-kubeflow-workflows/issues/43
https://github.com/canonical/charmed-kubeflow-workflows/issues/49

The rest:

https://github.com/canonical/charmed-kubeflow-workflows/issues/28
https://github.com/canonical/charmed-kubeflow-workflows/issues/31
https://github.com/canonical/charmed-kubeflow-workflows/issues/32
https://github.com/canonical/charmed-kubeflow-workflows/issues/35
https://github.com/canonical/bundle-kubeflow/issues/783, https://github.com/canonical/bundle-kubeflow/issues/785, and https://github.com/canonical/bundle-kubeflow/issues/817
https://github.com/canonical/bundle-kubeflow/issues/784
https://github.com/canonical/bundle-kubeflow/issues/816
https://github.com/canonical/charmed-kubeflow-workflows/issues/46
https://github.com/canonical/charmed-kubeflow-workflows/issues/48
https://github.com/canonical/kubeflow-rocks/issues/77
https://github.com/canonical/charmed-kubeflow-workflows/issues/29

When is the task considered done

All issues above have either been resolved or we have decided to skip/postpone those.

canonical / bundle-kubeflow

ci(rocks): tracker to tackle issues we bump on often across our rocks repos #765

Why it needs to get done

What needs to get done

When is the task considered done