Design provider agnostic API

[rucarrol-goog]

The goal of this ticket is to outline the work involved in designing a provider agnostic interface which can be re-used.

[rucarrol-goog]

Given this will be an interface to a controller, which has WiFi APs, which contain SSIDs, which contain clients, at a very minimum level we will need the following abilities:

• Fetch new controller connection
• Fetch new AccessPoint connection
• Fetch SSIDs From AccessPoint(Or Controller?)
• Fetch Client Data From SSIDs/AccessPoint/Controller
• Generalised fetch metric from Client function
• Generalised fetch metric from AccessPoint function
• Generalised fetch metric from Controller function

We'll concentrate on read only for now.

@awlx : Are there use-cases, operations or other things I am not aware of here?

[awlx]

@rucarrol-goog the unifi_client talks only to the controller as all informations can be fetched from there :). So all stats are actually fetched from there and then loaded into the corresponding dataclasses atm.

[rucarrol-goog]

@awlx Sure - but I'm talking about building a controller, AP and SSID agnostic set of operations.