Discussion: Mock Harbor Instance via GH Actions for testing

[NucleoFusion]

This is an issue to discuss the working and integration of a local harbor instance for running tests.
We need to have a similar format to how container-registry/harbor-satellite starts a mock server, but in GH Actions if I recall correctly.

https://github.com/container-registry/harbor-satellite/blob/main/.dagger/e2e.go
(This is the Dagger setup)

https://github.com/container-registry/harbor-satellite/tree/main/test/e2e/testconfig
(These are the required config)

We only need a few of these services not all, but we would require adding LDAP, preheat providers and other setups as well in the long run.
What are your thoughts?
@bupd @qcserestipy

[qcserestipy]

I was wondering whether this should have Priority: Critical even, since we always stumble upon it when talking about testing. And I agree that we can reuse a subset of the harbor-satellite setup. Probably it makes sense to introduce the smallest needed Harbor instance for testing at first and add other services such as LDAP in a step-wise fashion when needed.

[NucleoFusion]

Yep, except from what I see, harbor-satellite has it in Dagger instead of GH Actions. Which I think @bupd wanted in the last meet.