* googletest packages (libgtest-dev and libgmock-dev) have pkg-config
  files now. So, the build and installation steps are no longer
  required.

* Here are the installation information about these packages:
  $ $ apt list --installed libgtest-dev libgmock-dev
  Listing... Done
  libgmock-dev/glinux-rodete-base-20220316.03.07,now 1.11.0-3 amd64
  [installed]
  libgtest-dev/glinux-rodete-base-20220316.03.07,now 1.11.0-3 amd64
  [installed]

  $dpkg -L libgtest-dev | grep gtest.pc
  /usr/lib/x86_64-linux-gnu/pkgconfig/gtest.pc

  $ dpkg -L libgmock-dev | grep gmock.pc
  /usr/lib/x86_64-linux-gnu/pkgconfig/gmock.pc

* Adding libabsl-dev package as it's required by libchrome.

Bug: 227287284
Tag: #floss
Test: ./biuld.py --target docs and ./build.py
Change-Id: I46c9f16ce328041c8953c5ad2b513719997fb096

Bug: 231535626
Test: cert/run
QA testing before submit

Change-Id: I2be64c3db39e35ff4b31de4714634e77670338c3

This CL adds support for handling a simple PDL file which defines a
packet. The CL includes infrastructure for testing the generated code
against known-good output. This is sometimes called “snapshot
testing”. While there are crates for this, we currently don’t use any
to avoid pulling in new dependencies.

Bug: 228306440
Test: atest pdl_inline_tests
Change-Id: If33403444ba9e4ce9c45e15b65c1da03011aa5e9

* Migrate legacy ACTS-based tests to the new Blueberry mobly based
  framework:
      GattNotifyTest
      GattConnectTest
* Add associated libraries to support these tests
* client_port is no longer needed in config file

Test: gd/cert/run --sl4a_sl4a
Test: gd/cert/run --sl4a
Tag: #stability
Bug: 232048916
Change-Id: I680661d75dcd203c3f050b3379a01523275ec5b7

Seems like it fails with isolated:true, might need some
fixes in test assumptions.

Test: presubmit
Bug: 178498003
Change-Id: I4e1e526969cb6cb38a6c989ce4f517893e644816

Bug: 227487676
Test: cert/run
Change-Id: Ifb833c6109fc2dc4b0a1c0a14be185ecb1fd8296

Bug: 231970192
Tag: #floss
Test: ./build.py and emerge-zork floss
Change-Id: Ide87f94db9c7cdac837f96caef469754d8bef802

Bug: 227136187
Tag: #refactor
Test: gd/cert/run
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: I0b97e8efff55c001b319809605404d7faef6a2d8

Test: gd/cert/run LeAclManagerTest
Test: gd/cert/run SecurityTest
Fix: 231745328
Change-Id: Iefb3592b5869459adfd0196f9b3c20a2c4cf3745

Bug: 231373910
Tag: #refactor
Test: gd/cert/run
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: I84b650ea59284166b4d82f761abb3fec9fbda261

Bug: 193716447
Tag: #refactor
Test: gd/cert/run

Change-Id: I034f759e5ef4974dae67d5788ec54c25abf1832b

Bug: 230796293
Tag: #refactor
Test: gd/cert/run
BYPASS_LONG_LINES_REASON: Bluetooth likes 120 lines

Change-Id: Id30367eed441173e9c333cd2d8e259bb9fe700d9

* changes:
  Pass connection parameter to OnLeConnectSuccess
  LE Shim: Implement ReadRemoteControllerInformation

Bug: 231580214
Test: atest --host bluetooth_vc_test
Sponsor: @jpawlowski
Change-Id: Ib894ab01916d7eb989db6a0c28b79b321dd82ad6

Bug: 231095722
Tag: #refactor
Test: gd/cert/run
Change-Id: I6322c99ce880fb68966c4f1a25e5602ed8f36f84

Bug: 231095722
Tag: #refactor
Test: gd/cert/run
Change-Id: Id973755e3d259ad10d774882ebd546e0271b4d01

Aligning the definition with enum BluetoothDeviceType in Chromium.
In case topshim gets an invalid device type from libbluetooth,
it will be converted to 'Unknown' device type for correctness and
clarity.

Bug: 231248387
Tag: #floss
Test: manual test on classic and dual mode devices
Change-Id: Ieac91b26f13958ce974f528ac476f85594beb08b

To create SL4A_SL4A postsubmit pipeline, Mobly test runner is required per test script. (go/gd-sl4a-onboard)

Bug: 231518629
Change-Id: Id610b639730f4b8f107b3a036c9b4ca848e18774
Test: gd/cert/run

Make it so that AddPhy does not segfaults when called with no argument
and send a proper response when called with correct arguments.

Test: manually send add_phy commands with correct/incorrect arguments.

Change-Id: Idfd84ed5e994469ac69ec30e408abe3662ec7290

By default, it appears that the
PackageManager#SetComponentEnabledSetting() function used to allow
profiles to enable and disable their owned dependencies is actually
asynchronous. This means that there is currently a race between the
system flushing these changes so they take effect and Bluetooth (or
other components) wanting to use the dependency.

This change adds the PackageManager.SYNCHRONOUS flag to make the calls
to SetComponentAvailable always be in effect after the call completes.

Tag: #stability
Bug: 229629444
Test: atest BluetoothInstrumentationTest
Merged-In: I689d314e3afba884a7949e6f0c39157a668bbf92
Change-Id: I689d314e3afba884a7949e6f0c39157a668bbf92

Introduced in ag/17225723

Test: no
Bug: 217448211
Change-Id: I3e02721d4f48efc25c1a65af38967ccaa6ee9f09