[roll] Roll fuchsia [chromium][security] Add policies for chromium-system-tests

Add the "/core/test_manager/chromium-system-tests:**" moniker to each
policy that includes "/core/test_manager/chromium-tests:**".
This matches the behavior before https://fxrev.dev/801602 and the
subsequent switch to run tests in the new realm.

This should unblock Chromium (https://crbug.com/1418788). We'll look
into removing some instances of these monikers once everything is
working correctly.

Original-Bug: 121700, chromium:1418788
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/809428
Original-Revision: b8289b78af2dfabb07ecf48f868b7608fe490d7c
GitOrigin-RevId: 01a62ad976a921e7faa181c037b1e33add17bf06
Change-Id: I0d3f064ef82c395877095a65bbe6af43cac58e1b
1 file changed
tree: c0c897ceeaa16005808718f03788b08022a5b59d
  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.