Fill L2 Information in the initial provisioning configuration.

Since CMD_UPDATE_L2INFO has been removed from IpClient#StoppedState,
which was used to update the initial l2key and groupHint parameters,
pass these two params in the initial provisioning configuration
instead, then IpClient gets l2key and groupHint when starting prov
before DhcpClient starts.

This patch also removes the redundant updateLayer2Information call
after supplicant state COMPLETED. We can rely on the updated current
BSSID in handleSupplicantStateChange to detect if L2 roaming happened
and then trigger DNAv4/DNAv6 probe. The call graph when L2 roaming
happened looks like:

- WiFi is trying to associate to another AP
- supplicant state changes
- L2Key and GroupHint pair changes
- updateLayer2Information
    - IpClient already in StartedState, will process CMD_UPDATE_L2INFO.
    - DNAv4/v6 probe if updated bssid doesn't equal to current one.
    - Rebind IP Lease if needed.
    - update the current bssid on IpClient side.
- complete 802.1x AUTH
- supplicant state changes(supplicate.COMPLETE)
- updateLayer2Information // this is redundant, remove it.

Bug: 131797393
Test: atest FrameworksWifiTests
Change-Id: If3167c3f831283d5a63a7099baa243c8d4ac9921

0 files changed, 0 insertions, 0 deletions