[roll] Roll fuchsia [build][idk] Validate metadata file schema in merged IDK

Validate the schema of the JSON metadata files after merging the IDK.

The validations in sdk_atom() and sdk_collection() are retained until
the in-tree IDK, which does not use `generate_idk`, validates the
schema.

Also add missing schema files to //build/sdk/meta.

Remove "maxProperties" from "binaries" in loadab_module.json as the
limit of "2" is exceeded when validating the merged manifest and other
schema files do not limit the number of CPU architectures.

NO_IFTTT=Just moving the list within this file.

Original-Bug: 413071161
Test: `fx build //sdk:final_fuchsia_idk.exported` with and without "debug_libs" removed from //build/sdk/meta/sysroot.json
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1260847
Original-Revision: 8f5d3393f72145c1c11a362dae93a0bf2dfc7951
GitOrigin-RevId: 2fd427a99c31d85852a4b3504348a19205b8873c
Change-Id: Ie247cff530e19516e06266bdd727363052b283ef
1 file changed
tree: a8b4f40a8ea8721227e81b8d56a06f63169835bd
  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.