[roll] Roll fuchsia [display][banjo][fidl] Revise layer composition op representation.

This CL's main goal is to fix the naming issues of the Banjo type
ClientCompositionOpcode.
1. Each instance represents multiple operations, but the name suggest
   that each instance is one operation.
2. The name over-indexes on the way that the type is currently used.

This CL also aligns the FIDL interface to the Banjo interface, and
cleans up the comments for DisplayEngine.CheckConfiguration(), which
is where the composition opcodes type is used.

Original-Bug: 316631158
Test: fx test //src/graphics/display (no functional change)
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1169272
Original-Revision: 512662b5e40a9378762482dd98b4b134ecf96d6e
GitOrigin-RevId: b8dde9238f3cd30061b8e78a6261267d38f61684
Change-Id: I084cc7540147f6bf5d9790e32e269de4759b9592
1 file changed
tree: b5cd8a0e442b6a559db1a813c706194e954ec690
  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.