Implement common CI workflows for all charm repositories

[ca-scribner]

Context

Much of our charm repository CI is implemented in each repository rather than centrally. This causes issues like:

• to fix a bug, we must change the workflow in all repositories
• it is easy for us to miss some repositories when we push changes, leading to divergence between what we think is common code across our repositories

This has been partly addressed in the past through things like the common quality check workflow, but we should extend this to all our CI files similar to what we did for our rocks CI.

Roadblocks for this task include:

• slight differences between the CI in our different repositories. For example, some repos might use the integrate tox environment while others use integration. Some others might have integrate-SomeSpecialCase. This needs to be standardized
• sometimes we need additional tests or configuration in a repository. How can we achieve that while otherwise staying common?

What needs to get done

1. summarize what all our charm repositories do so we know what capabilities we need
2. implement shared workflows that support all our repositories
3. implement template CI files, like we have for rocks

Definition of Done

1. all (or as many as possible) charmed kubeflow charm repositories are using common CI files from a central repository

[syncronize-issues-to-jira]

Thank you for reporting us your feedback!

The internal ticket has been created: https://warthogs.atlassian.net/browse/KF-5453.

This message was autogenerated