Pin the platform2 repo to a certain commit in build.py and add a missing
default USE flag required by common-mk. We only depend on common-mk for
building so pinning is fine for this repo only.

Bug: 264776587
Tag: #floss
Test: ./floss/build/build-in-podman.py
Change-Id: I1e274473eb756a9ceac078e10ae7f48cd6f0bd05

* changes:
  unittest: main:: Use common log msg
  unittest: stack:: Use common log msg
  unittest: btif:: Use common log msg
  unittest: bta:: Use common log msg

Currently, the number of remaining bytes is not computed correctly,
which may led to buffer overflows.

Bug: 264568677
Test: atest AdvertiseDataParserTest
Change-Id: I8004f471859fb373a4fe0fbe295be7b258481d9f

Test: manual
Bug: 264469240

Change-Id: I14115e04c959c3d3e4c15a075c997c2a7fb2f667

* changes:
  Remove second action on tBTA_DM_PM_SPEC
  Use system property for sniff idle time in HS
  Use lazy static initialization

Because of recursion, we think we are starting the wrong module in the
error crash
"Can't start stack, last instance: starting Btaa Module" while it's
stuck on hci

Test: None
Bug: 261263171
Change-Id: If7d87a7c98c2190f1db9de84a1c6f5de814d4f2d

* changes:
  btm_iso: Add ISO tracking to btm dumpsys
  gatt: Improve logging

Implemented everything available, with exceptions needing call history,
redialing, call hold/resume functionality, as well as a few tests that
failed for reasons I can't figure out.

Bug: 264637071
Test: atest pts-bot:HFP/HF
Change-Id: I203dfaf802a07a73a470181fc3a328d59c9cff84

L2CAP/COS/CED/BV-03-C
L2CAP/COS/CFC/BV-01-C
L2CAP/COS/CFC/BV-02-C
L2CAP/COS/CFC/BV-03-C
L2CAP/COS/CFC/BV-04-C
L2CAP/COS/IEX/BV-02-C
L2CAP/COS/ECH/BV-01-C
L2CAP/EXF/BV-01-C
L2CAP/EXF/BV-02-C
L2CAP/EXF/BV-03-C
L2CAP/EXF/BV-05-C

Test: atest pts-bot:L2CAP -v
Change-Id: Id3c63f97d137d8525ec8c9f44a389b0cf2c6cc7b

This reverts commit 9d76f0b7.

Reason for revert: breaks aosp_arm64-userdebug_tidy

Bug: 264648327
Change-Id: I7de1704c412ddb236456e9e6c44f074c704c0896

This reverts commit 3886f1a7.

Reason for revert: cause test failure b/264616183

Change-Id: Ief6e5972a55501cb0bbc1632c0d29a7daa49353d

Setting the promise before removing the value was making some tests
flaky because they assumed that the value was removed when the promise
returned which happened most of the time until it didn't

Bug: 264500085
Test: bluetooth_test_gd_unit64 --gtest_filter=QueueTest.* --gtest_repeat=-1
Change-Id: I951e21b78d971966a40d3c53aa1c26caa532f0df