[inspect][ctf] Use default publish settings in Inspect tests

This makes the CTF Inspect publisher test use default PublishOptions.

Sometime ago it seemed better to me to not encode our defaults into CTF
tests. However, with the addition of name-filter-lists in selectors, I
now think it is better to have CTF ensure that if you
  1) Publish using the default Inspect tree name
you will always be able to
  2) Select from Archivist without specifying a name filter list.

Before the use of name-filter-lists in selectors, the tree name was
mostly an internal detail. Now it is part of the selector API, so
ensuring these behaviors stay consistent is important.

Bug: 355732696
Change-Id: I7d00b9d7f9b9e625b3833faac2d99defc75e3461
2 files changed
tree: 2086af260879c8c626ca58276da57513cb8e2ed6
  1. boards/
  2. build/
  3. bundles/
  4. docs/
  5. examples/
  6. infra/
  7. products/
  8. scripts/
  9. sdk/
  10. src/
  11. third_party/
  12. tools/
  13. zircon/
  14. .clang-format
  15. .clang-tidy
  16. .editorconfig
  17. .git-blame-ignore-revs
  18. .gitattributes
  19. .gitignore
  20. .gitmodules
  21. .gn
  22. .ignore
  23. analysis_options.yaml
  24. AUTHORS
  25. BUILD.gn
  26. CODE_OF_CONDUCT.md
  27. CONTRIBUTING.md
  28. fuchsia.code-workspace
  29. LICENSE
  30. OWNERS
  31. PATENTS
  32. pyproject.toml
  33. pyrightconfig.json
  34. README.md
  35. rustfmt.toml
  36. shac.star
  37. shac.textproto
README.md

Fuchsia

What is Fuchsia?

Fuchsia is an open source, general purpose operating system supporting modern 64-bit Intel and ARM processors.

We expect everyone interacting with our project to respect our code of conduct.

Read more about Fuchsia's principles.

How can I build and run Fuchsia?

See Getting Started.

Where can I learn more about Fuchsia?

See fuchsia.dev.