[Enhancement] Refactor backend's ChipTool class

[ccruzagralopes]

Description

Currently, the ChipTool class handles:

• SDK container lifetime
• SDK YAML runner setup and use
• chip-tool/app binaries execution for commissioning/decommissioning

And it will handle even more once the SDK python tests are integrated.

Additional Information

Comment from @mikaelhm in the PR project-chip/certification-tool-backend#29:

I'm wondering if we need some refactoring of this ChipTool class (maybe not needed for this PR)

But it's getting quite bloated, and it's really hard to follow what exactly is happening in a method like this.

I think we should split it in three classes:

• ChipCertBinsContainer
• ChipTool (covering running chip-tool/chip-app)
• MatterSDKRunner (for running yaml tests)

[ccruzagralopes]

Done in:

• [Refactoring] Remove "tool" from most chiptool occurrences certification-tool-backend#48
• [Refactoring] Create SDKContainer class certification-tool-backend#52
• [Refactoring] Replace ChipTool with ChipServer and MatterYAMLRunner certification-tool-backend#57