[roll] Roll fuchsia [sc] Print possible alternatives in validation errors.

For structured config we always package value files with .cvf extensions
so we can skip printing anything else.

Example:

```
Product Assembly Failed
    1.  Validating product assembly failed:
    └── Failed to validate bootfs:
        └── meta/archivist.cm: Validating structured configuration
            └── Couldn't find component's config values in package.
            └── `meta/archivist.cvf` does not exist in bootfs.
                Possible alternatives with the same extension: [
                    meta/console.cvf,
                    meta/fshost.cvf,
                ]
```

Original-Fixed: 99525
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/677892
Original-Revision: 37008f2c39dcf68304a62e0833c22a9c20344d00
GitOrigin-RevId: ec2f6f586fd64ec868b0824db7eebb3d9e96cdc2
Change-Id: I6aed6d11ab1ad121918acfd1ffbffc9a4a097103
1 file changed
tree: 0e4ebcc9adf3ffbc1f3b44da47e3be9724616a5b
  1. infra/
  2. third_party/
  3. cts
  4. firmware
  5. flower
  6. fortune-teller
  7. jiri.lock
  8. minimal
  9. prebuilts
  10. README.md
  11. stem
  12. test_durations
  13. 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.