Refactoring to remove "interface" types

[rootwarp]

Checklist

• New Feature for the SVC/Plugin
• New Feature for CI/CD
• Enhancement on Vatz
• Others(etc. e.g, documentation,...)

---

Please describe, what it's about or related Problem with

A clear description of what feature need to be developed or enhanced in Vatz

interface type is using too much all of the code base.
But it could be serious problem in near future because,

• This means source code is not self-documented. Developer can't understand code easily if variables are defined as interface type
• interface type can be broken in runtime. We should test really hard by checking every possible values.
• And that means development pace will be slow down.

Describe the output that you are expecting for above

A clear and concise description of what you expect to happen.

Avoid to use interface type if possible.

Describe alternatives you've considered

A clear and concise description of any alternative solutions or features you've considered.

This refactoring task will be huge job and also will be affected to other tasks that are on going.
So I suggest do refactoring task by module one by one.

Additional context

Add any other context or screenshots about the feature request here.

---

Child issues.

• Refactoring executor module #179
• Refactoring notification module #181
• Refactoring healthcheck module #203

[rootwarp]

@xellos00 What do you think of my suggestion?

[xellos00]

@rootwarp
I understand your concern, Can we prioritize all issue in order first unless you want to proceed this issue in this Sprint.

[rootwarp]

@rootwarp I understand your concern, Can we prioritize all issue in order unless you want to proceed this issue in this Sprint.

Yup.

[xellos00]

@xellos00
Task

• Remove any Type in interface.
• Maximize Unit test.

[xellos00]

I will close this issue as all sub-issue has finished.