update firmwares: SR: X.3.10.0.133 MR: X.5.7.0.42

SR:
- Bug Fix: Scan: Scheduled Scan to 16 hidden profiles is performed every 1
  second after P2P Client connected to GOUT. While moving from band to
  band inside a cycle, Connection scan process set its state to PENDING
  w/o scheduling a timer, which might cause to a race between Beacon TX
  guard interval update and Connection scan process.
  Fix: Avoiding the state change to pending while moving from band to band.
- Bug Fix:protecting TimeSchedulerChangeScanToPendingCB() with DISABLE_INT()
  so it won't be cut by TxNotifyTriggeredScanCB(). This is a fix for race
  scenario in which we are alreay inside TimeSchedulerChangeScanToPendingCB(),
  clearing the eventHandler, then cut by TxNotifyTriggeredScanCB which check
  the eventHandler, and when it sees that it is 0, it moves the scan process
  to pending. Then the process scheduler is invoked, moves the scan process to
  running, and then we return back to the TimeSchedulerChangeScanToPendingCB()
  context, which moves back the process scan to pending state.

MR:
- Bug Fix: When AP/GO is started and it is connected to STA, FW sets a guard
  interval between Beacon Tx to Scan's processes of 25mSec. The motivation of
  this fix is to leave a guard interval after Beacon Tx for STAs to get out
  from PS to receive packets from AP. To achieve this goal scan in now is
  limited to 70mSec in case AP is connected to STA.
  Note: If next Scan's time event should be invoked in 500uSec or less don't
  update time event.
- Bug Fix: (Process Calibration) If there is an active role tune back to the
  operational channel & band after calibration completes. This cause an AP/GO
  to operate on a wrong channel , i.e AP/GO transmits beacons on a wrong
  channel.
- Bug Fix: Scan: Scheduled Scan to 16 hidden profiles is performed every 1
  second after P2P Client connected to GOUT. While moving from band to
  band inside a cycle, Connection scan process set its state to PENDING
  w/o scheduling a timer, which might cause to a race between Beacon TX
  guard interval update and Connection scan process.
  Fix: Avoiding the state change to pending while moving from band to band.
- Bug Fix: solve an IOP issue with the Galaxy S3. We saw that when we use
  AP/GO role, a galaxy S3 is connected to us, and we run TCP TX traffic,
  the traffic stops after some short time. After an investigation, we saw
  that the Galaxy, becomes deaf for a short time, and we try to send packets
  to it but get to the station aging max retries, and remove that peer from
  us which cause traffic stop. We saw that after some time the galaxy recovers
  from this deafness and transmit to us again, but it's too late, we already
  removed it. To overcome this:
  a.  In station aging, after exceeding MAX_TX_RETRIES for the specific peer
      for the first time, we suspend the TX of the galaxy's flid, and
      initialize a timer with ANOTHER_CHANCE_FOR_AGING_DURATION (for now 1
      sec). After the timer exceeds, we resume the traffic, and try to send
      packets to the galaxy again, if we get one more time to MAX_TX_RETRY
      only then we remove the station.
  b.  There was a change in the ieee802.11n spec which allows us to transmit
      BAR frames in 11b + OFDM 6/12/24 Mbps Rates we saw that it helps to
      reduce the galaxy's deafness problem.
- Reducing the gLogger UART keep alive message interval from 5sec to 1sec
  (UART_KEEP_ALIVE_INTERVAL)

Signed-off-by: Ido Reis <idor@ti.com>