[roll] Roll fuchsia [lsc] Migrate all clients of fuchsia.sys2.ComponentResolver

This LSC migrates all usages of the `fuchsia.sys2.ComponentResolver`
protocol to `fuchsia.component.resolution.Resolver`. The latter is in
the SDK and the former will be removed after this CL. This was done
in an LSC, instead of a soft transition for the following reasons:

* All usages are in-tree, so we're confident that nothing will break.
* The change is mechanical. That is, it only changes one namespace to
another, and as such it's fair to assume that nothing will break.
* A soft transition would have greatly slowed down the rollout
of `fuchsia.component.resolution.Resolver`.
* It would have been tricky to have `component_manager` support
consuming both protocols at the same time.

Original-Bug: 94581

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/656983
Original-Revision: 28e39762b3aaec2c3d3bf4d1b29fbb87ca1e1848
GitOrigin-RevId: a31efe32d3846c26dd249d9fae590988061f5576
Change-Id: I97272d94d22217dcf960c74b61239fc93b32f9e8
1 file changed
tree: d88559ab0385f317f5af85ba58b53a81779a9a42
  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.