Refactor bluetooth_proxy and (esp32_)ble_client/beacon/tracker/server to be platform agnostic

**Describe the problem you have/What new integration you would like**

Refactor `bluetooth_proxy` and `esp32_ble_x`(x=client/beacon/tracker/server) to be platform agnostic with agnostic APIs/classes.

**Please describe your use case for this integration and alternatives you've tried:**

Eventually expand bluetooth proxy to non-ESP32 platforms, such as `bk72xx` and `rtl87xx`. Right now all bluetooth functions are heavily influenced and designed around ESP32/idf headers and structures.

**Additional context**

I'm not requesting a full implementation of any of the bluetooth functionality on other platforms (at least yet), but rather getting the ball rolling so others don't have to decide on what would or would not be a breaking change or what the standard of the APIs should look like.

It seems like the newer standard has been to name the component after the core functionality without consideration for the platform, and just have separate `_platform.c/h` files, and that is the approach I would like to see here.