Should Activate utility be migrated to an AtActivationClient interface and implementation in the api package? #334
Description
Is your feature request related to a problem? Please describe.
The SDK should provide a consistent API for all the features. Activation features are arguably distinct from the AtClient API but currently exposed as a utility class which feels incongruous
Describe the solution you'd like
Suggestion: new AtActivationClient interface that mirrors AtClient
Describe alternatives you've considered
No response
Additional context
No response