Refactor move inbound mail parser to worker

[djabarovgeorge]

What change does this PR introduce?

Move the inbound mail parser worker to the worker app.

Why was this change needed?

There is no reason for us to spin the inbound mail parser worker in the API app.

Other information (Screenshots)

[scopsy]

Just a note, it will require a terraform change aswell* cc @Cliftonz

[LetItRock]

from the code perspective it looks good to me! 🔥
@Cliftonz we would need to implement appropriate cloud infra changes after this PR is merged

[Cliftonz]

@djabarovgeorge I see the spell check failing for the moment.

however I want to confirm that now the workers will be processing the inbound mail and it will go like:

email -> dns -> inbound-email service-> queue -> email parse (on worker) -> standard queue

If this is true then we can merge this in and the general worker service should be able to handle this.

[djabarovgeorge]

email -> dns -> inbound-email service-> queue -> email parse (on worker) -> standard queue

@Cliftonz It will be even shorter
email -> dns -> inbound-email service-> queue -> email parse (on worker)
After we parse the email we respond user's webhook

[Cliftonz]

@djabarovgeorge Then I do not think we need to make any changes as the general worker service can handle the load of at most 10 jobs per month.

[Cliftonz]

@djabarovgeorge There are a few conflicts but I would like to get this merged in soon

[netlify]

❌ Deploy Preview for dev-web-novu failed.

Name	Link
🔨 Latest commit	5d8b78b
🔍 Latest deploy log	https://app.netlify.com/sites/dev-web-novu/deploys/65b8d0dd0a7b670008d1e457

[djabarovgeorge]

@djabarovgeorge There are a few conflicts but I would like to get this merged in soon

Tend to agree here 💪