[roll] Roll fuchsia [bazel] Add host tests for json_validator_valico

This CL adds three small host Bazel tests for the json_validator_valico
program, that is already built with Bazel. The GN tests are not removed
yet, since Bazel host tests are still not visible to `fx test` and
infra.

This demonstrates how to use the new host_test() Bazel rule to define
a series of tests using the same binary with different arguments, and
how to locate data files using a runfiles library.

- json_validator_valico_test.py: A test wrapper Python script that
  runs the tool against a test schema and a test document and
  verifies whether it succeeds or fails.

  This uses a Python runfiles library to locate the test's runtime
  dependencies, following Bazel test conventions.

- defs.bzl: Add a macro to define a py_test() target that runs the
  tool against fixed test schemas and documents, invoking
  json_validator_valico_test.py.

- BUILD.bazel: Add three new tests, and a test_suite() that is
  reference from //build/bazel/host_tests/BUILD.bazel

Testing manually with:

```
fx bazel test --config=host //build/tools/json_validator/test:tests
```

Or by building then invoking one of the test directly:

```
fx build --host @//build/tools/json_validator/test:tests
bazel-bin/build/tools/json_validator/test/json_validator_valico_base_test
```

Original-Bug: 349341932
Original-Reviewed-on: https://fuchsia-review.googlesource.com/c/fuchsia/+/1511236
Original-Revision: cfa3dab89e820e9dde45e0c488fb795f97507613
GitOrigin-RevId: 2f1a1e30cfd99b7c3cf9699b6b15ee3b6cfc9a65
Change-Id: I723b37c93a2b2282547851ed51f1d78a92fd7fac
1 file changed
tree: e30b79bdfe606955cc606206bc0db25243ff5306
  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.