[roll] Roll fuchsia [bt][a2dp][avrcp] Untangle A2DP/AVRCP core shards

Now that optional capability routes exit, we can independently include
A2DP and AVRCP on products that need both.

Mark the PeerManager capability as optional as the A2DP component will
function even if it is not available.

Original-Bug: 107401
Test: fx build
Manual: fx reboot, verify bt-a2dp.cm and bt-avrcp.cm start OK.
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/714879
Original-Revision: baee5664dea18c502df43b578b42d31bae302fda
GitOrigin-RevId: d0c9d5f1dfdd1b86deadcda3a2da073c7953b36b
Change-Id: I9903ceae521da1e9768389b3a523ffb6d2eb199b
1 file changed
tree: a6b02ad0769c8c257c6bf2e6b6fdc6819f72433a
  1. git-hooks/
  2. infra/
  3. third_party/
  4. cts
  5. firmware
  6. flower
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. toolchain
README.md

Integration

This repository contains Fuchsia's Global Integration manifest files.

Making changes

All changes should be made to the internal version of this repository. Our infrastructure automatically updates this version when the internal one changes.

Currently all changes must be made by a Google employee. Non-Google employees wishing to make a change can ask for assistance via the IRC channel #fuchsia on Freenode.

Obtaining the source

First install Jiri.

Next run:

$ jiri init
$ jiri import minimal https://fuchsia.googlesource.com/integration
$ jiri update

Third party

Third party projects should have their own subdirectory in ./third_party.