[roll] Roll fuchsia [session] Remove builtin runner + boot resolver session-env

We route some capabilities to the session that it does not use, and are
only used to launch platform components. To protect against an unwanted
dependency in the future, remove them from the session's environment.

These capabilities are:

- boot-resolver: For launching fuchsia-boot components
- builtin_runner: For launching builtin components (components in
  component_manager). An example is the elf runner component.

In the case of #2, we are adding more builtin components, which were
designed only for platform use.

Original-Fixed: 375000535
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1146981
Original-Revision: 9f24dd261eb63855986e877acf7bfd83bd1c1cc7
GitOrigin-RevId: 24078a28b798d8836085b3ea247689e78b97d830
Change-Id: I1746785619982cbebd280dc237b80d0661b162c8
1 file changed
tree: 1bbe64407a344309de5f64b57e2b782839db0463
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cts
  6. firmware
  7. flower
  8. jiri.lock
  9. MILESTONE
  10. minimal
  11. prebuilts
  12. README.md
  13. stem
  14. test_durations
  15. 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 in one of the communication channels documented at get involved.

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.