EasyConnect Seperation of Concerns Refactor

[bcarlson-dev]

• Separated Controller, Proxy Agent, and Enrollee into different classes for better code understanding
• Introduced ec_manager

[tuckerpo-cl]

Stylistically I'd like to see override used in subclasses where applicable, just makes reasoning about the code easier for instance if you're reading a subclass header, immediately obvious that a given function extends some other base class. Also, regarding send_action_frame as a param for ec_manager, would that be bound to send_frame, or some new entry into em_agent which sends action frames via the bus to onewifi? Other than this comment and the other 2 left, LGTM.

[bcarlson-dev]

Stylistically I'd like to see override used in subclasses where applicable, just makes reasoning about the code easier for instance if you're reading a subclass header, immediately obvious that a given function extends some other base class. Also, regarding send_action_frame as a param for ec_manager, would that be bound to send_frame, or some new entry into em_agent which sends action frames via the bus to onewifi? Other than this comment and the other 2 left, LGTM.

I added the override and totally agree. I meant to do it but got mixed up in the fact that C++ doesn't require it.

Regarding the send_action_frame that'll need to be a new function definition in em_agent that utilizes the OneWifi "Device.WiFi.AccessPoint.{i}.RawFrame.Mgmt.Action.Tx" call.