[roll] Roll fuchsia [fidlc] Implement RFC-0232 multiple version selection

This CL implements "RFC-0232: FIDL bindings for multiple API levels" in
fidlc, and changes the GN build from using `--available fuchsia:LEGACY`
to using `--available fuchsia:15,16,17,18,19,20,NEXT,HEAD`. The list of
supported API levels is derived from //sdk/version_history.json.

FIDL files still have `legacy=true` attributes, but fidlc now reports an
error if a `legacy` attribute is inconsistent with the set of supported
API levels. A follow-up change will remove the `legacy` argument.

There is one limitation: when targeting 2+ versions, the set of versions
must include HEAD. This limitation is implicit in how LEGACY works, and
keeping it makes the transition easier. It will be lifted in the future.

Test: fx test fidlc-test
Original-Bug: 42085274
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/955053
Original-Revision: 348c348a678ec05dc54b69c20bc903b8163bd5b4
GitOrigin-RevId: 5d94ee4c1a59a46efe0d7a63461a174e89d54c15
Change-Id: I3d77d4cec60cbac5cdb7002004547a2683b39564
1 file changed
tree: 6609c253aa8e7aa399c5abe7f85a233516011c25
  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.