[roll] Roll fuchsia [cm_fidl_analyzer] Add resolver registry to analyzer's environment

The capability route static analyzer keeps track of
the environment associated to each component instance,
but previously didn't include resolvers in its per-
environment data store. This change adds a simpler
copy of component manager's ResolverRegistry type to
the analyzer.

Original-Bug: 61861
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/585005
Original-Revision: 16a81ae886c251cf5d4cb6ea00b0e7709188090b
GitOrigin-RevId: 7d5c9c5107ddf369290082677cb90e1a2717ae13
Change-Id: I9d6180b2e29529b6bb3a2e2d270ab792d00ff5dd
1 file changed
tree: 850a499aaf3a4a8e0fb2e335c5c5a99908a918b4
  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.