[roll] Roll fuchsia [bt] Remove RfcommTest routes and define testonly manifests

Remove capability routes to `RfcommTest` so that it is not available in
production environments.

Instead, define testonly manifests with the capability routes. Users
will need to manually update core.cml to point to the testonly manifest
if needed. At this time, we do not want to go through the process of
making #bluetooth-core product variable.

Remove appmgr route to RfcommTest as it will be routed through the
testonly manifest.

Define a testonly group for Bluetooth core. This can be included in the
relevant product.gni file to set up a special BT realm for testing
scenarios.

Original-Bug: 86390
Test: fx build && manually verify bluetooth-core starts up okay
Test: fx build with bt-init-testonly.cml and verify RfcommTest is
available

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/653224
Original-Revision: f1baaa79706adb41b1e69bf4843eddb5187430f2
GitOrigin-RevId: da3de1a9f100aefc97a4949c878d6f265127184d
Change-Id: Ic9cbd26fb061a470fc4c2d1fc3cf1f30b8a08511
1 file changed
tree: 2e5a326cc8d33e4b02018621c5fc737849d52dc5
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. jiri.lock
  7. minimal
  8. prebuilts
  9. README.md
  10. stem
  11. test_durations
  12. 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.