Update images to use agreed registries

[kimwnasptd]

This is a follow-up from #118

Once we'll have agreed to which image names to use then we can go and update the components' manifests and CI files to use the udpated image names.

Note though, that this can happen even if we haven't yet configured the repo to have permissions to publish to the ghcr.io registry. As long as we fix #119 then the integration tests will always be building locally the images they need. Thus the tests should be able to pass, even if images are not yet published.

But of course the publish worklflows will be failing as long as we don't give permissions to the repo to publish to the corresponding registry.

Some existing PRs for this are:

1. ci: Migrate kubeflow/kubeflow prof_controller_docker_publish.yaml GitHub Action to kubeflow/dashboard #117
2. chore: make dashboard release-able (part 1) #115
3. ci: Migrate kubeflow/kubeflow centraldb_angular_docker_publish.yaml G… #114

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity.
It will be closed if no further activity occurs.
Thank you for your contributions.

Members may comment /lifecycle frozen to prevent this issue from being marked as stale.

[github-actions]

This issue has been automatically closed because it has not had recent activity.

Members may comment /reopen to reopen it.