Roll recipe dependencies (trivial).

This is an automated CL created by the recipe roller. This CL rolls
recipe changes from upstream projects (chromiumos_config, recipe_engine) into this repository.

The build that created this CL was
https://ci.chromium.org/b/8681803437692614241

chromiumos_config:
https://chromium.googlesource.com/chromiumos/config.git/+log/62cde77d92b489d614302875bf8f871cbebb6632~..5240855674efae76ae1e32177b4128c1f975573a
  62cde77 (bbrotherton@google.com)
      pasit: add observing_camera to PasitHost Device proto
  5240855 (otabek@google.com)
      Define DownloadFile gRPC request and response messages.

recipe_engine:
https://chromium.googlesource.com/infra/luci/recipes-py.git/+/3414dbec0b4f93c6e9e76cc25ac1d8c0b234f265
  3414dbe (chanli@google.com)
      [TurboCI] QueryNodesRequest->ReadWorkPlanRequest: do not set empty

Please check the following references for more information:
- autoroller, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#autoroller
- rollback, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/workflow.md#rollback
- cross-repo dependencies, https://chromium.googlesource.com/infra/luci/recipes-py/+/main/doc/cross_repo.md

Use https://goo.gl/noib3a to file a bug.

Recipe-Tryjob-Bypass-Reason: Autoroller
Ignore-Freeze: Autoroller
Bugdroid-Send-Email: False
Change-Id: I7b13e80c1fb69f9002f7226c1d3f7c35125d996e
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/infra/proto/+/7848003
Commit-Queue: recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
Bot-Commit: recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com <recipe-mega-autoroller@chops-service-accounts.iam.gserviceaccount.com>
1 file changed
tree: ced1f60d9ea02e7ec9fb35308e1ba07e37c731c8
  1. bin/
  2. extern/
  3. gen/
  4. go/
  5. infra/
  6. recipes/
  7. src/
  8. .gitattributes
  9. .gitignore
  10. buf.yaml
  11. generate.sh
  12. LICENSE
  13. OWNERS
  14. OWNERS.tse
  15. PRESUBMIT.cfg
  16. PRESUBMIT.py
  17. README.md
  18. setup_cipd.sh
  19. unblocked_terms.txt
README.md

infra/proto

infra/proto vs chromite/infra/proto

This repository exists in two locations in the tree: infra/proto, and chromite/infra/proto. The infra/proto repository is always at ToT, while the chromite/infra/proto checkout is branched to allow the proto there to (more) accurately reflect the version of the proto the Build API is using.

When making changes to the proto that you need to test in the Build API, you will need ensure the changes are applied to the chromite/infra/proto checkout. Chromite generates its proto bindings from the chromite/infra/proto repo.