Bluetooth: Controller: Direction finding samples do not reconnect after disconnection

[cvinayak]

Describe the bug
Some direction finding tests have started to fail in nRF Connect SDK testing. The issue is investigated and it is happening only with Zephyr Controller which is used as lower tester against SDC upper dut.

The problem is happening even in very simple scenario as

 Connect - Disconnect  - Connect

The second connection is not established at all.

• It is happening with both roles (peripheral, central)
• it is happening when DF is enabled (CONFIG_BT_CTLR_DF)
• it is not happening when SDC is used in both upper and lower
• it is not happening with babblesim

Derived a simple central-peripheral app from existing DF samples (direction_finding_central/peripheral) in sdk-zephyr in here

To Reproduce
Steps to reproduce the behavior:

1. Used the modified direction_finding_peripheral sample, to restart advertising on disconnect
2. mkdir build/direction_finding_central; cd build/direction_finding_central
3. cmake -DBOARD=nrf52833dk_nrf52833 ../samples/bluetooth/direction_finding_central
4. ninja
5. ninja flash
6. Repeat steps 2 - 5 for direction_finding_peripheral
7. In a terminal window observe the central establish connection with peripheral
8. Reset the central and check that central is able to connect back to peripheral which has restarted advertising
9. Vice versa can be tested by resetting the peripheral and central should connect back.
10. The failure is, central and peripheral do not connect back after disconnection

Expected behavior
Central and Peripheral shall connect back after disconnection

Impact
showstopper

Logs and console output
TBD

Environment (please complete the following information):

• OS: Linux
• Toolchain: Zephyr SDK
• Commit SHA: as in the description

Additional context
NA