Fix profiles being marked as FORBIDDEN before bonding is attempted.

Consider folowing scenario:

1. Device connects over LE transport. Service discovery is triggered.
2. UUIDS discovered event is propagated through stack, profile
   connection is triggered, which can mark some profiles as FORBIDDEN.
3. Bonding is triggered during same connection.
4. Service discovery, and DIS read is triggered after bonding.
5. Profile connection can't happen, because some profiles were already
   marked as FORBIDDEN in steap 2.

Only Battery Service is allowed to connect while not bonded, therefore
separate profile connection logic to treat it separately, and deal with
remaining profiles only when BONDING or BONDED.

Bug: 356325069
Bug: 355109861
Flag: unbonded_profile_forbid_fix
Test: perform subsequent FP pairing couple of times
Change-Id: I5bc5559b8e9007d6f41d313f170b935e50d50bcc