Set up semi-automated track creation procedures for all charmed kubeflow repositories

### What needs to get done

Charmhub has developed a semi-automated method for track creation, as described [here](https://discourse.charmhub.io/t/self-service-creation-of-tracks-now-available-to-charm-developers/10910) and [here](https://discourse.charmhub.io/t/how-to-create-a-track-for-your-charm/11102). We should use this in all our charms to reduce the manual effort during bundle release.

### Why it needs to get done

The current process requires a manual request for each charmhub track created (~30 per release). Automating this would speed up the release process (both in engineering hours and calendar time) and make it more deterministic

Start with the two linked Charmhub procedures and map the current manual track-request process across the Charmed Kubeflow repositories. Identify how bundle releases currently create tracks; done means a semi-automated procedure is available for every charm and removes the repeated manual requests.

Written by the indexing model from the issue text.