floss: Avoid extra authentication for a secure RFCOMM connection

When a RFCOMM client initiates a secure connection with a temporary link
key,  it will trigger an additional authentication with MTIM protection.
The second connection not only takes extra time but also leads to RFCOMM
disconnection from the RFCOMM server running on some Android 11 devices.

This behavior was introduced in the commit 6fa9d175
(“Add RFCOMM_CreateConnectionWithSecurity”).
This patch addresses the issue by updating the security record during
RFCOMM connection setup, eliminating unnecessary authentication

Bug: 312840315
Bug: 316824288
Tag: #floss
Test: CTS verifier 11r8 Bluetooth tests, using Pixel 4 as server
Test: m -j

Change-Id: I5f0a71b474460efcc396ea5e0c053db72e5a5abe