Move postgres controller code to package, cleanup crds, fix minor issues

[mploski]

Description

What does this PR have in it?

Key Changes

Highlight the updates in specific files

Testing and Verification

How did you test these changes? What automated tests are added?

Related Issues

Jira tickets, GitHub issues, Support tickets...

PR Checklist

• Code changes adhere to the project's coding standards.
• Relevant unit and integration tests are included.
• Documentation has been updated accordingly.
• All tests pass locally.
• The PR description follows the project's guidelines.

[github-actions]

CLA Assistant Lite bot:
Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contribution License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment with the exact sentence copied from below.

---

I have read the CLA Document and I hereby sign the CLA

---

_{You can retrigger this bot by commenting recheck in this Pull Request}

[DmytroPI-dev]

We have pkg/postgresql/database/core/types.go and pkg/postgresql/cluster/core/types.go, both in core package, can we have some conflicts here?

[mploski]

We have pkg/postgresql/database/core/types.go and pkg/postgresql/cluster/core/types.go, both in core package, can we have some conflicts here?

We might, in this case we can have separate "shared" directory with reusable types later on. Currently most of the things are not shared

[limak9182]

Nit: Is that a requirement for SOK? I wasn't testing the code against two parallel goroutines running at the same time. Does it work such that one worker starts on an event, but if it's still processing and another event comes in, it doesn't just sit in the queue, it can be picked up by another worker? I’d like to trigger that for future local tests, that's why I’m asking.

[mploski]

They just asked us to provide this info explicit. Yes your assumption is correct how it works, with one exception: if changes is related to the same CR it still will be queued to provide proper serialisation