Split wifi state for AP and STA

[bugadani]

Closes #210

I wonder what to do with the combined get_wifi_state() function in the long run. If esp-wifi ever gets AP-STA support, picking one state will be difficult. Maybe the current "none of these modes? then invalid" logic will be good enough, or maybe that function can be removed altogether. I'm not sure.

I've removed a bunch of possibilities from the set of states, based on what I found here. If it weren't a breaking change, I have also renamed the event-like ApStop, etc. enum variants to a more grammatically proper form (e.g. ApStopped).

[bjoernQ]

From a brief look this looks good to me. I think I'm fine with renaming the enum variants at this point of time. (t.b.h given the upcoming breaking changes in the next esp-hal release this is a really minor break)

[MabezDev]

LGTM, shame about portable atomic but its something we can resolve in the future :)

[bugadani]

Sooo... do you think we can move forward with this? 🙃

[bjoernQ]

There two are new

warning: unnecessary `unsafe` block
  --> esp-wifi\src\wifi\os_adapter.rs:45:5
   |
45 |     unsafe { get_sta_state() == WifiState::StaConnected }
   |     ^^^^^^ unnecessary `unsafe` block
   |
   = note: `#[warn(unused_unsafe)]` on by default



warning: unnecessary `unsafe` block
    --> esp-wifi\src\wifi\mod.rs:1462:13
     |
1462 |             unsafe {
     |             ^^^^^^ unnecessary `unsafe` block

Then I guess it's fine

[bjoernQ]

LGTM