[roll] Roll fuchsia [driver_runtime][rust] Add driver server

Implements a `DriverServer` that interfaces between the driver host and
the rust driver object, including managing its async lifetime. This is
analogous to the C++ `DriverServer`.

Also adds the basic outline of a `Driver` trait that is kind of like
C++'s `DriverBase`, except that instead of holding the context in a base
class it is given a `DriverContext` with that information.

As part of this, this also breaks up the main `fdf_rust` library so that
`fdf_sys` is its own (visibility-gated) library that both `fdf_rust` and
`fdf_rust_server` depend on. This avoids a dependency loop since the
server depends on generated driver transport fidl, which in turn depends
on `fdf_rust` for things like Channels.

Original-Fixed: 359228261
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1090314
Original-Revision: 40c310645b9e2c2501b11efb8ed28cd63c27de1b
GitOrigin-RevId: 4321a28ed06e24656fd3f9ee9c49a96d3693f438
Change-Id: Ie716475857e2b474d78f7bff0fc05ee2db3e9240
1 file changed
tree: 8985b49c1edcf84d55a63a7c20fa6675f460fa02
  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.