[roll] Roll fuchsia [fidlc][fidlgen_cpp] Expose request/response in declaration_order

Given a method `Protocol.Foo`, we generate request/response structs
named `ProtocolFooRequest` and `ProtocolFooTopResponse`. These
declarations are present in the "declarations" block in the JSON IR, but
not "declaration_order", which is relied on mainly by C++ codegens.

In order to start generating C++ request/response domain objects, this
CL first makes those decls look more like regular structs by adding them
to "declaration_order".

fidlgens that don't rely on "declaration_order" are not affected.
Filtering is added to other fidlgens to keep output unchanged.

Subsequently, the unified C++ bindings generator would start outputting
C++ objects for these declarations.

Test: fx regen-goldens
Test: fx exec src/devices/tools/fidlgen_banjo/regen_banjo_tests.sh
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/603682
Original-Revision: 57675c08c47e0cacb014e0e5e605bac697b34b5a
GitOrigin-RevId: e35db65c5052ac3ee74d25adbbcbfc8a3e51db52
Change-Id: If6ef90019c50618e991cc508d79661934538e73d
1 file changed
tree: 7a99642e9b9ed5a866cd4a1a2ce745a137a5d7bc
  1. infra/
  2. third_party/
  3. firmware
  4. flower
  5. jiri.lock
  6. minimal
  7. prebuilts
  8. README.md
  9. stem
  10. 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 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.