[roll] Roll fuchsia [bazel][host] Add host constraints for host examples

... and build them in GN with `host = true` Bazel action wrappers.

These examples were previously building on targets instead of hosts.
This was revealed when I migrated rules_python from WORKSPACE to bzlmod,
and pytoolchain resolution for fuchsia_x64 started failing, which
somehow worked in WORKSPACE.

NOTE: This adds one extra bazel action, which I don't expect any build
slowdown because it doesn't require the Bazel SDK and should be
parallelized very early in the build graph.

Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1273745
Original-Revision: fabfd978f8934672be9a292b961652dee722db97
GitOrigin-RevId: 44c6a1602a4a7dac8d5627e999f75594102bfb48
Change-Id: I022156d73860aafee4a0eee7fc90913a913d0c9c
1 file changed
tree: ab349eaac7f32f31f180007f8bf7e62fd3019a3c
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. flower
  6. jiri.lock
  7. MILESTONE
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. 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 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.