Handling AKM based checks in connect path

Cleanup AKM based checks, in connect path, which are restricted to legacy AKMs
and extend these checks to newer AKMs (SAE-EXT-KEY/SAE-EXT-FT-KEY)

Bug: 289991109

Test: Tested connection to WPA2 AP and confirmed from logs that that two AKMs are
     sent to driver in connect command.
Test: EVT platform.

Signed-off-by: Mir Ali <mir-khizer.ali@broadcom.corp-partner.google.com>
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:81f06b0d90e679fdf393a0a773467ad60aa44b49)
Merged-In: I0910a4fbb0cd39eef174d38e27301ef16a43b74a
Change-Id: I0910a4fbb0cd39eef174d38e27301ef16a43b74a
1 file changed