feat: release APIs and Operator independently

[thisthat]

You can see the tags created in my fork here: https://github.com/thisthat/open-feature-operator/tags

For the Operator, the release works as previously creating containers and publishing them to a registry: https://github.com/thisthat/open-feature-operator/actions/runs/6861654249

For the APIs, only a tag is created: https://github.com/thisthat/open-feature-operator/actions/runs/6861600403

This PR covers only the release process. We should also move all go files into two different go modules.
This entails the following:

1. Creating a go.mod file under the apis folder
2. Remove dependency from utils in the new apis pkg (it is used in alpha1 and alpha2)

[codecov]

Codecov Report

Merging #541 (a31fb4d) into main (a97d336) will decrease coverage by 4.88%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #541      +/-   ##
==========================================
- Coverage   82.81%   77.94%   -4.88%     
==========================================
  Files          24       10      -14     
  Lines        1437     1020     -417     
==========================================
- Hits         1190      795     -395     
+ Misses        209      189      -20     
+ Partials       38       36       -2     

see 14 files with indirect coverage changes

Flag	Coverage Δ
unit-tests	77.94% <ø> (-4.88%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

[thisthat]

we should decide what should be the first version of the APIs package.

[toddbaert]

I think same version as the current package makes sense...?

[beeme1mr]

This will slightly change how the release process works. @toddbaert and I have dealt with this enough times that it shouldn't be an issue here.

[toddbaert]

👍

[beeme1mr]

I didn't know this was an option.

[toddbaert]

I'm 100% on board with this.

[thisthat]

Nice, then I'll work on this PR making it fully working ;)

[thisthat]

To continue with this PR, I would need a tag for the /apis package. @toddbaert maybe we can have a sync and add that manually for the first release of the APIs :)
Otherwise, we can use the local "replace" in the operator go.mod until we do the first official apis release and live with a failing docker build for a while.