Unify/refactor domain delete procedures (auction on/off, delete/force delete)

[artur-intech]

No description provided.

[yulgolem]

So in order to incapsulate domain managing (at least deletion) procedures we are to use Interactor design pattern (https://mkdev.me/en/posts/a-couple-of-words-about-interactors-in-rails).

The main point of this refactoring is to unify domain behaviour. For example, we are using DomainDeleteConfirmJob for domain deletion, but methods of domain instance (described in concerns/domain/force_delete) for setting ForceDelete status on a domain.

By introducing interactors we'll gain single incapsulated source of changes related to task, so we should put there all the notifications etc.

For implementation we'll need to do the following refactoring:

• ForceDelete procedure (Refactor ForceDelete to use Interactor pattern #1740 ).

• Cancelling ForceDelete (Refactor canceling ForceDelete process to use Interactor pattern #1743 ).

• start_client_hold procedure from Concerns::Job::ForceDelete (Refactor setting ClientHold to use interactor design pattern #1751).

• DomainDeleteConfirmEmailJob (Move DomainDeleteCongirmJob to interactor #1753)

• Update WhoisRecord (Move WhoisUpdate job to interactor #1772 )

• DomainDeleteConfirm (domain release processing) (Move DomainDeleteConfirm job to interactor #1769)

• DomainDeleteJob (Move DomainDeleteJob content to interactor #1755)

• DomainUpdateConfirmJob (Move DomainUpdateConfirmJob to interactor #1760)

• All the DomainCron tasks, they must be just called from DomainCron (Move DomainCron tasks to interactor #1767)

[yulgolem]

Everything is done, the task might be closed now.

[vohmar]

done, thank you!