Add docker-compose file to e2e

[cYKatherine]

No description provided.

[gmsdelmundo]

I think we can add a profile in publicoperator service called public_operator: (https://docs.docker.com/compose/profiles/)

Then, when calling docker compose up:

• If we're building a public operator, the public_operator profile can be set and publicoperator service will be spun up
• For private operator builds, don't pass a profile as an argument, and the publicoperator service will not be started

But this can be done later on when working on private operator pipelines

[cYKatherine]

I think we can add a profile in publicoperator service called public_operator: (https://docs.docker.com/compose/profiles/)

Then, when calling docker compose up:

• If we're building a public operator, the public_operator profile can be set and publicoperator service will be spun up
• For private operator builds, don't pass a profile as an argument, and the publicoperator service will not be started

But this can be done later on when working on private operator pipelines

My understanding from the setup for uid2-dev-workspace is that the only difference between spinning up a public operator and a private one is that the latter one is using local-e2e-docker-private-config.json while the public one is using local-e2e-docker-public-config.json.

In this action, I passed the operator type as an input, and it will also be used here to determine whether it's a public operator or a private one. The default value is set to be public so we will use it as a public operator by default. wdyt?

@gmsdelmundo

[gmsdelmundo]

I think it would be better to set this to uid2-core:latest so that it can still be run locally

Then the regex in the pipeline script should be updated to capture uid2-core:latest rather than <CORE_VERSION>

Same applies for other versions in this file