[roll] Roll fuchsia [bt][avrcp] Enable AVRCP as v2 component

Update core.cml with bt-avrcp, and route capabilities used/exposed by
it. Expose AVRCP capabilities to appmgr to be available to v1
components.

Remove sysmgr mappings to the v1 AVRCP component.

Update the Triage rule to include the v2 moniker for the selector. Both
v1 and v2 monikers are maintained as part of a soft transition per the
migration guidelines.

Original-Bug: 73933
Test: fx test bt-avrcp-tests, fx test bt-avrcp-integration-tests, fx
test bt-avrcp-smoke-test
Test: Manual - reboot device and verify AVRCP launching correctly
Test: fx iquery show core/bt-avrcp
Test: bt-avrcp-controller 1234 - verify bt-avrcp.cm is spun up and
successful PeerManager connection.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/543561
Original-Revision: 9a3fa5d9456b397c3989147090cb430391c1d862
GitOrigin-RevId: 5f90ae3538e7bc8f903488ea4b215dc963c1634b
Change-Id: Ic54a23ec05e6dc019dd682e8c168a4054cdeaa86
1 file changed
tree: 404d2107eedc4b083d2932affad71e837314aae9
  1. garnet/
  2. infra/
  3. peridot/
  4. third_party/
  5. topaz/
  6. zircon/
  7. firmware
  8. flower
  9. jiri.lock
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
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.