Wrong address provided in discovery report when a bonded device with RPA is discovered.

[h2zero]

Checklist

• Checked the issue tracker for similar issues to ensure this is not a duplicate
• Read the documentation to confirm the issue is not addressed there and your configuration is set correctly
• Tested with the latest version to ensure the issue hasn't been fixed

How often does this bug occurs?

always

Expected behavior

Get the OTA address to make a connection.

Actual behavior (suspected bug)

Getting the ID address which cannot be used for connecting.

Error logs or terminal output

Steps to reproduce the behavior

Bond with a device using RPA
Disconnect
Scan for the device
Attempt to connect

Project release version

latest

System architecture

Intel/AMD 64-bit (modern PC, older Mac)

Operating system

Linux

Operating system version

Mint 21

Shell

ZSH

Additional context

Using an original esp32, host based privacy enabled, when scanning the device report is showing the ID address of the bonded device instead of the OTA address so the esp32 is not able to connect to that device.

This was an old issue that was fixed here: #7.
The regression was in 56917b2

More info: h2zero/esp-nimble-cpp#356 (comment)