Refactor dns flows and workers

[Genne23v]

Close #315
Close #333

• Split DNS module into two phases (DB and DNS)
• Specify type to each flow, worker and job
• Change name to subdomain or fqdn to distinguish

How to test

Currently integration is only set up in /dev route. You don't need any environment setup to test.

I'm not sure how DNS handling should be initiated after DB update (same frontend call or background job).
@dadolhay This update requires DB table ID in addDnsRequest call in your function. Please let me know if you have any concern with this approach.

[humphd]

@Genne23v it would have been better to separate the new functionality you've added from the refactoring. Is there any way to split this PR into smaller PRs?

If not, I'll review it as is. But this isn't ideal.

[Genne23v]

I can separate. I will push an update soon.

[Genne23v]

@humphd I have removed new functionalities although they are very small. I would appreciate your review.

[humphd]

Can you rebase and fix CI before I review?

[Genne23v]

Can you rebase and fix CI before I review?

Let me connect with frontend that is just merged.

[Genne23v]

@humphd @dadolhay I connected DNS module with frontend. It's functional, but it needs more backend error validation and display the error somewhere in frontend. Let me know if anything needs to be added.

[Genne23v]

@dadolhay @humphd I updated the PR. I would appreciate another round of review!

[humphd]

I've made an initial set of comments. Looking good.

[humphd]

Two small things. This is looking so much better, great work.

[humphd]

Only took 2 days, not bad!