[roll] Roll fuchsia [incoming_cpp] Prepare `component::Clone` for removal of `Node.Clone`

As part of the io2 migration, the `fuchsia.io/Node` protocol will
compose `fuchsia.unknown/Cloneable.Clone`. This allows us to reuse the
same implementation when cloning arbitrary channels as long as we know
the protocol is `Cloneable`.

To prepare for this end state, we remove the type tags used to override
protocol resolution, since these assertions will fail once the Node
protocol also composes Cloneable.

For now, we unconditionally call `fuchsia.io/Node.Clone` as long as the
protocol composes one of the node protocols. Once all out-of-tree
fuchsia.io servers have support for Cloneable.Clone2, we can update
`component::Clone` accordingly.

Original-Bug: 374768831
Test: component_cpp_incoming_tests
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1141993
Original-Revision: c3cc49606acf3e12fb4de84019deec67b2b4df9f
GitOrigin-RevId: 38219aea7eb9a8707bb2df43318a0c51630c0929
Change-Id: Iadcebdab588fac6f4b1869214f147a1bdaf17cdb
1 file changed
tree: 68eba52ab3a37e2f82b21f34f9990b6d180f0ccc
  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.