Fix various issues with wireless information under FreeBSD:
Fix various issues with wireless information under FreeBSD:

- Instead of hoping that the currently associated AP will show up as
  the first AP in the list of scan results, fetch the BSSID of the
  currently associated AP and use that to fetch station info for the
  AP.  This provides more frequently updated signal strength
  information than scan results and reliably provides information when
  multiple APs are in range.
- Do not treat the RSSI value as a raw signal value in dBm.  Instead, use
  the same formula as ifconfig(8) to compute a signal value.
- Do not report the beacon interval value as a signal quality level.

Dettorer/i3status,flammi/i3status,peder2tm/i3status-netdev,JSmith-BitFlipper/i3status,ixjlyons/i3status,lbonn/i3status,jasperla/i3status,Dettorer/i3status,jasperla/i3status,i3/i3status,ixjlyons/i3status,lexszero/i3status,peder2tm/i3status-netdev,i3/i3status,Gravemind/i3status,Watcom/i3status,opntr/i3status,flammi/i3status,lbonn/i3status,bsdjhb/i3status,flammi/i3status,Dettorer/i3status,ixjlyons/i3status,opntr/i3status,JSmith-BitFlipper/i3status,lbonn/i3status,peder2tm/i3status-netdev,Gravemind/i3status,jasperla/i3status,bsdjhb/i3status,lexszero/i3status,opntr/i3status,JSmith-BitFlipper/i3status,Watcom/i3status,jasperla/i3status,Watcom/i3status,flammi/i3status,bsdjhb/i3status,i3/i3status,lexszero/i3status,Dettorer/i3status,Watcom/i3status,bsdjhb/i3status,opntr/i3status,lexszero/i3status,JSmith-BitFlipper/i3status,Gravemind/i3status,ixjlyons/i3status,lbonn/i3status,i3/i3status,Gravemind/i3status,peder2tm/i3status-netdev