Move binary logging to sys crate

[MabezDev]

Thank you for your contribution!

We appreciate the time and effort you've put into this pull request.
To help us review it efficiently, please ensure you've gone through the following checklist:

Submission Checklist 📝

• I have updated existing examples or added new ones (if applicable).
• I have used cargo xtask fmt-packages command to ensure that all changed code is formatted correctly.
• My changes were added to the CHANGELOG.md in the proper section.
• I have added necessary changes to user code to the Migration Guide.
• My changes are in accordance to the esp-rs API guidelines

Extra:

• I have read the CONTRIBUTING.md guide and followed its instructions.

Pull Request Details 📖

Closes #1932

Depends on esp-rs/esp-wifi-sys#477

Moves the logging methods to the sys crate to avoid duplicate definitions. ieee driver now takes RADIO_CLK by value, so that only wifi or IEEE can be enabled at once. In the future we'll want to relax this to use Peripheral.

[MabezDev]

I'm tempted to write a test case, but the test case would be empty as I'm only going to check that the two drivers can be linked together. Do we think this is worth while?

[MabezDev]

This was definitely wrong, I hope it wasn't breaking something 😅

[bjoernQ]

I'm tempted to write a test case, but the test case would be empty as I'm only going to check that the two drivers can be linked together. Do we think this is worth while?

I guess a test that just gets compiled and linked is nice - flashing a huge test which doesn't do anything is probably wasteful

[bjoernQ]

Nice! I wanted to do this (or something similar) for quite some time but always forgot about it

[bugadani]

Weeee, finally, we have real frequencies :D

[bjoernQ]

We need to activate the log/defmt features in esp-wifi-sys (depending on the features of esp-wifi/esp-ieee802154)

[bjoernQ]

There is one new warning while building

warning: creating a shared reference to mutable static is discouraged
   --> C:\projects\review\mabez\esp-hal\esp-ieee802154\src\fmt.rs:114:21
    |
114 |             let _ = ($( & $x ),*);
    |                     ^^^^^^^^^^^^^ shared reference to mutable static
    |
   ::: C:\projects\review\mabez\esp-hal\esp-ieee802154\src\raw.rs:385:13
    |
385 |             trace!("Received raw {:x?}", RX_BUFFER);
    |             --------------------------------------- in this macro invocation
    |
    = note: for more information, see issue #114447 <https://github.com/rust-lang/rust/issues/114447>
    = note: this will be a hard error in the 2024 edition
    = note: this shared reference has lifetime `'static`, but if the static ever gets mutated, or a mutable reference is created, then any further use of this shared reference is Undefined Behavior
    = note: `#[warn(static_mut_refs)]` on by default
    = note: this warning originates in the macro `trace` (in Nightly builds, run with -Z macro-backtrace for more info)
help: use `addr_of!` instead to create a raw pointer
    |
114 |             let _ = addr_of!(RX_BUFFER);
    |                     ~~~~~~~~~~~~~~~~~~~

[bjoernQ]

Thanks!

[jessebraham]

LGTM, thanks!