sdk-nrf: v2.7.0
When PAWR is enabled I no longer get connection timeouts as a callback to bt_conn_cb.connected with the conn_err parameter set when attempting to open a connection as a central.
Instead I get an error log from inside bt_hci_core.
Code to start connection
```
struct bt_conn_le_create_param con_params = BT_CONN_LE_CREATE_PARAM_INIT(BT_CONN_LE_OPT_NONE, BT_GAP_SCAN_FAST_INTERVAL, BT_GAP_SCAN_FAST_INTERVAL);
con_params.timeout = 500;
err = bt_conn_le_create(&target_address, &con_params, BT_LE_CONN_PARAM_DEFAULT, &conn);
```
Logs I get
```
00> rtt:~$ [0:0:5.943,420] <dbg> EDGE_HEARTBEAT_PERIPHERAL: connect_to_peripheral: attempted connection start
00> rtt:~$ rtt:~$ [0:0:10.943,298] <err> bt_hci_core: Invalid connection complete event
```
I have validated this is from PAWR by disabling it and confirming I do get the expected callback.
Flags enabled when we use PAWR
select BT_OBSERVER
select BT_EXT_ADV
select BT_CTLR_ADV_EXT
select BT_PER_ADV_SYNC
select BT_PER_ADV_SYNC_RSP
select BT_PER_ADV_SYNC_TRANSFER_SENDER
select BT_PER_ADV_SYNC_TRANSFER_RECEIVER
select BT_CTLR_SYNC_PERIODIC
select BT_CTLR_SYNC_PERIODIC_RSP