Keep pack-specific logic outside of the SDK

[eddie-knight]

This needs discussion from contributors!

I'd propose that we remove pack-specific logic, such as the Kubernetes code currently found in this repo

Reasons:

• decreases clarity when looking at service packs, requiring contributors to bounce over to the SDK to learn about test-specific code
• decreases clarity of what the SDK is intended for
• If shared code exists between a vanilla pack & a provider-specific pack, it could be argued that the logical place for the common code to exist is within the vanilla pack

[lluuiissoo]

100% agree with this. SDK is a bit bloated at the moment.

SDK responsibility should be: To enable the creation of a new Service Pack, regardless of technology / business logic.
Functions:

• Wrapper around remote plugin implementation so that new SP can hook into core runner
• Provide interface for consistent logs
• Provide interface for consistent config settings

[lluuiissoo]

Any K8s and Azure specific logic/helpers should be removed from SDK into their own repos