hci: implement set random MAC address

[xudongzheng]

No description provided.

[aykevl]

I'm a bit hesitant with this PR because it's a bit more complicated than that: there are three different kinds of random MAC addresses. See this post for details: https://novelbits.io/bluetooth-address-privacy-ble/. This PR doesn't distinguish between the three, which means the API will need to change in the future.

I plan on implementing private addresses in the bluetooth package eventually, after implementing pairing and bonding.

[xudongzheng]

That sounds reasonable. I'll mark the PR as a draft for now until there is a bit more clarity around how MAC addresses should be stored internally.

I'll keep this semi-updated as it's useful for #230.

[deadprogram]

Hello @xudongzheng and @aykevl I was just looking at this PR, and thinking that it probably seems fine.

Via the linked article:

IMPORTANT NOTE: All Bluetooth devices must use one of either type: a Public Address or a Random Static Address.
The next type of address (Private Address) is optional and is solely used to address privacy concerns (i.e. device may use one of them in addition to either a Public or Random Static Address).

The HCI controller command does not distinguish between different kinds of random addresses.

See https://analog-devices-msdk.github.io/MAX-BLE-HCI/le_controller_cmds.html#set-random-address

Creating a random address that fulfills the extra requirements of private addresses can be added using an additional API of some kind, but seems like something additional. As such, this PR probably seems like a good thing.

Thoughts?

[deadprogram]

See https://analog-devices-msdk.github.io/MAX-BLE-HCI/le_controller_cmds.html#set-address-resolution-enable for example.

[deadprogram]

I resolved merge conflicts in a local branch and tested. Works as promised!

See my PR #325 and #326

[deadprogram]

Closing this PR since it was replaced by your commits in #325

Thanks for working on this @xudongzheng