Planning for the future with regards to RF support

[jessebraham]

At the time of writing, this repository is currently a bit of a sandbox, an experimental project containing code for both Wi-Fi and Bluetooth. Eventually, I believe these should be split into separate packages.

While we're obviously not ready for this step yet, this brings up the question on how we want to handle these packages moving forward. I think it's worth keeping in mind that when the ESP32-H2 is finally made generally available, we will eventually need to add support for IEEE802.15.4 radios as well (which is absolutely not a near-term project, just to be clear).

Two options I can think of are:

1. Use this repository as a monorepo, renaming it to something like esp-rf; this would contain esp-wifi, esp-bt, and esp-???, or whatever these packages will ultimately be named
2. Create separate repositories for each package

While it likely doesn't matter too much which approach we choose, once we have further developed these packages it may make one choice the clear path forward (eg. if we end up with one or more packages which are commonly used across all three aforementioned libraries, but which are not generally helpful elsewhere, might make sense to go the monorepo route).

This doesn't require any real conversation any time soon, I just wanted to make my thoughts on this public.

[bjoernQ]

One thing to keep in mind: At least for BT and WIFI they are not completely independent. At least the BT driver uses (parts of) the WIFI drivers. Certainly, no idea what upcoming drivers will be like

Besides that, I'd probably go for a monorepo - especially since things are pretty much related to each other and changes in one crate might need changes in other crates. With individual repos that becomes a burden