[roll] Roll fuchsia [bazel_sdk] Clarify fuchsia_component() component_name tests

The component name can come from three sources. Clarify exactly which
scenario each of the cases defined in `_test_setting_component_names()`
is testing.

Original-Original-Bug: 525461025
Test: fx build //build/bazel/bazel_sdk:bazel_sdk_tests
Original-Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1671618
Original-Original-Revision: a9a2dfd15a2b25290fc9dbcf3accb929a101b767
GitOrigin-RevId: d82544ccac28984f7ed161e39fc94a9331ef9dd4
Change-Id: Ie76041333cce0f2bc0c5bbc59f79149ca2b6a968
Reviewed-on: https://fuchsia-review.googlesource.com/c/integration/+/1673057
Cr-Commit-Position: refs/heads/main@{#195302}
1 file changed
tree: 3e8929d18dde8beba258dced61093357426fce5a
  1. ctf/
  2. git-hooks/
  3. infra/
  4. third_party/
  5. cobalt
  6. flower
  7. jiri.lock
  8. MILESTONE
  9. minimal
  10. prebuilts
  11. README.md
  12. stem
  13. 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 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.