[roll] Roll fuchsia [assembly] Add developer overrides template

Adds a template for providing developer overrides to assembly.

Adds a new GN argument for specifying the use of a developer overrides
target with a given assembly target within the build:

Example:
    product_assembly_overrides = [
      {
        assembly = "//build/images/fuchsia/*"
        overrides = "//local:my_assembly_overrides"
      }
    ]

The assembly target is matched by GN label pattern.  And the overrides
are defined using the new template:

Example: (//local/BUILD.gn)

  import("//build/assembly/developer_overrides.gni")

  assembly_developer_overrides("my_assembly_overrides") {
    ...
  }

Original-Bug: b/327440885
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1008325
Original-Revision: 636e768186fa54f6d2325d60f80c365b32fef0c4
GitOrigin-RevId: 2b3936e8b5d1a263fcfbffd82c82d0343a9c242a
Change-Id: Ida1acc9fdf6f15941b5877edad7213bdd4bb7cdf
1 file changed
tree: c59a31ac4420a23f8d3ef5af7880bce12b9c2154
  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 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.