floss: Enable profiles in a certain good order

AVRCP and A2DP races to memset and allocate avct_ccb. If we're unlucky,
we might leave it at NULL so no incoming AVRCP profile can get through.
Effect varies on the peer devices, ranging to letting us initiating the
AVRCP to outright refusing any further transactions.

The effort to fix the race is tracked in b/286991526. For now, let's
just prevent the race by initiating the profiles in a known good order.

Bug: 312489181
Test: m -j
Test: Repeatedly restart floss and try accepting connection from a
      Bose 700. Verify it always works.

Flag: EXEMPT floss only changes

Change-Id: Idac7f00ed34e2fecef1abdc650eb09bda41556a1