feat(api): set integration as primary and priority system

[LetItRock]

What change does this PR introduce?

Set integration as "primary" endpoint and priority system logic:

1. One integration per channel could be marked as primary.
2. Only Email and SMS integrations could be marked as primary and will apply priority to the integrations. For the Chat and Push integrations messages are delivered for each channel, potentially different integrations, meaning that we can't have a "primary" integration concept or priority system. For In-App we only have one provider rn, but in future, we might have many per application, so there also we can't apply these concepts.
3. When we do create or update the first active integration (excluding Novu providers) for the Email or SMS channel, that integration will become automatically primary.
4. I will describe all the other logic in comments on the code.

Why was this change needed?

Other information (Screenshots)

[linear]

NV-2607 The BE Priority System logic for integrations

[djabarovgeorge]

Everything looks great! :) I just had a couple of questions sorry about it, if my concerns are by design I can approve it just let me know

another small thing i think create and update usecase shares some logic maybe we could extract it as well but totally could we for future refactoring.

[djabarovgeorge]

Yeah looks great to me awesome work :)