wlan: Initial forced roaming to 5GHz

If gEnableFirstScan2GOnly in .ini is set to 1 then
driver will scan only 2.4 based bss in first scan.
If a saved profile is present, then driver established
connection with 2.4 ghz based bss. So host need to check
if there is any roam-able candidate is present into the
5Ghz band so host can initiate a roaming to 5Ghz based bss
if 5Ghz ap is having better rssi by difference from
currently AP gNeighborInitialForcedRoamTo5GhRssiDiff.
To enable this feature gNeighborInitialForcedRoamTo5GhEnable
ini item need to set to 1

Change-Id: I71c1554fd8b09c5511de8337e720b7341d49c56c
CRs-Fixed: 701756
wlan: Fail to load driver if INI file is corrupted

Avoid over parsing of the INI buffer which leads to
memory corruption and fail the driver load if INI
buffer seems to be corrupt.

Change-Id: I3252d033ec6faea5f5979e8b631dc766a5c5dd1c
CRs-Fixed: 707317
wlan: Kernel Panic due to null pointer dereference.

Currently in csrIsSessionClientAndConnected function,
device mode is acessed from roamprofile without checking
if roamprofile exist or not.
As a part of fix added check to ensure that device mode
is obtained only when a valid roamprofile is available.

Change-Id: Iff2c05dfc88669f9689280342af422576ea78da0
CRs-Fixed: 714231
Wlan: Revision 3.2.3.405

Revision 3.2.3.405

Change-Id: I7c25049ff311d9731a403db1d29f909673e6f897
CRs-Fixed: 688141