Update generated code with previous changes (#324)

Improve phrasing of digest_function added in #311 (#312)

- Unlike the other messages where a digest_function field was added,
  ExecuteActionMetadata is returned by the server to the client. This
  means that the words "client" and "server" need to be swapped around
  in some but not all places.

- To ensure backward compatibility, we permit digest functions that were
  defined at the time this field was added to remain unset. When the
  digest_function fields were added to the other messages, the last one
  to be added was MURMUR3. In the meantime we've added BLAKE3 and
  SHA256TREE, so for this specific field we must list those as well.

Improve phrasing of digest_function added in #311 (#312)

- Unlike the other messages where a digest_function field was added,
  ExecuteActionMetadata is returned by the server to the client. This
  means that the words "client" and "server" need to be swapped around
  in some but not all places.

- To ensure backward compatibility, we permit digest functions that were
  defined at the time this field was added to remain unset. When the
  digest_function fields were added to the other messages, the last one
  to be added was MURMUR3. In the meantime we've added BLAKE3 and
  SHA256TREE, so for this specific field we must list those as well.

ExecuteActionMetadata requires digest_function (#311)

The specified ExecuteActionMetadata will have no association with the
digest_function requested in an execution, and cannot be used to
retrieve the action, without a digest_function associated with it.

Support digest functions in remote_asset API (#286)

* Support digest functions in remote_asset API

* Add digest_function to response and directory rpc

* change digest_function in responses to bool

* Revert "change digest_function in responses to bool"

This reverts commit a749638.

---------

Co-authored-by: Tyler Williams <williams.tyler@gmail.com>

inline hinting for ExecuteRequest (#287)

Match the capabilities of GetActionRequest to support hints for composing ActionResults for Execute

Allow emitting output directories as plain Directory messages (#258)

* Regenerate all .pb.go files

It looks like the current ones are out of sync.

* Allow emitting output directories as plain Directory messages

As part of #257 we're discussing adding support for storing directories
in Git's format. This means OutputDirectory.tree_digest will no longer
point to an actual recursive tree object (like REv2 Tree). Instead of
doing that, I would like to investigate whether we can add native
support for storing output directories in decomposed form.

Support multiple remote execution digest functions (#236)

Even though the cache can announce support for multiple digest
functions, the remote execution system cannot. Let's address this
inconsistency by adding a new repeated field that should in the (very)
long term replace the singular field.

Embed partial ExecutedActionMetadata in ExecuteOperationMetadata (#238)

* Add support for auxiliary operation metadata

* Hint at using ExecutedActionMetadata

* Embed ExecutedActionMetadata directly

Support multiple remote execution digest functions (#236)

Even though the cache can announce support for multiple digest
functions, the remote execution system cannot. Let's address this
inconsistency by adding a new repeated field that should in the (very)
long term replace the singular field.