Wireless Configuration and non supported features

[rjbrache]

Describe the bug 🪲
Currently the FW is not queried for supported wireless Encryption nor Authentication methods prior to trying to configure the FW with the supplied profiles. This can produce partial configuration and inaccurate result messages.

To Reproduce 🪜
-Use later FW which does not support TKIP encryption (AMT 16, 15, ???)
-Create some wireless profiles some using TKIP some using CCMP
-Create a profile which includes a mix of wireless profiles (both those specifying TKIP and those specifying CCMP)
-Activate/Provision the device with the created profile

Currently activation will end with a message stating "Failed to add wifi settings". However this is only 100% accurate if the first wireless profile uses TKIP encryption. Looking at the RPS logs shows that if there are CCMP profiles prior to the TKIP profile those do get added to the FW. Also, once one wireless profile fails, no attempt is made to configure with the other wireless profiles supplied.

Expected behavior
FW should be queried for supported encryption and authentication types via CIM_WiFiEndpointCapabilities methods (SupportedEncryptionMethods & SupportedAuthenticationMethods). If some of the supplied profiles specify unsupported settings a decision needs to be made as to whether or not to reject all supplied wireless profiles with a resultant message of "Failed to add wifi settings" or configure what is supported, ignoring the rest, and changing the resultant message to "Failed to add some wifi settings".

AMT Device (please complete the following information): 🖥️

• OS: linux and windows
• AMT Version: tested 15 and 16
• AMT Configuration Mode: tested ACM
• Network Configuration: tested Dynamic

Acceptance Criteria:

• Understand what features are no longer supported on new versions of AMT and provide an appropriate message to the user
• If the erroneous option in the profile can be bypassed, continue to activate/configure AMT and provide the error report in the summary