deployment complete

To determine the files to be uploaded, pipe the result of a find command
into en env var, id only tested it on a single file in the past - when
it has multiple files, it finds a new line character and terminates.

as such, release fails to upload assets.

Update `buf alpha plugin push` command to add support for installing
plugins from released versions (zip file containing buf.plugin.yaml and
image.tar). Remove all support for building Docker images (Docker CLI is
preferred).

This adds a performance benchmark for the image filtering logic, to make
sure the changes actually improve performance.

Performance is improved in two key ways:
1. Shedding the `protosource` model wrappers and instead directly using
   descriptor protos.
2. Accumulating results in one place, instead of repeated allocation and then
   concatenation of slices. (This is also useful pre-factoring for adding more
   improvements in the future.)

The net result is that it's now 1.7x as fast, uses 60% as much memory, and
performs less than 1/10th as many allocations.

Closes TCN-823.

Update `buf alpha plugin push` to first check if an existing image
digest exists in the OCI registry. If found, we can re-use it instead of
pushing a new tag of the same image.

This should also greatly improve the performance of pushing images when
the image already exists remotely.

* Add default, except override to managed mode `optimize_for` option
* preserves backward compatibility with the current `optimize_for`
option being string

Bump to the latest connect-go and pull in updates to other non-pinned go
dependencies.

The 'Remote' field contains the full plugin name (including path and
version information). For the GetRemoteHostname() method, we should
parse the hostname portion and return it.

This resolves 404 errors when generating with older plugins.

If the current digest has the same image ID as the image to push, we can
greatly speed up looking through every tag (which may contain multiple
duplicates - potentially one per version/revision of a plugin). This
should greatly speed up the lookup in the case where the plugin already
exists on the OCI registry.

If an enclosing message is not part of the transitive dependency graph,
but a nested message therein is, the enclosing message will be stripped
of its fields. This produces a smaller filtered descriptor set but does not
impede the use of the results for dynamic messages or dynamic RPC.

Similarly, if a method is indicated as a type filter, its enclosing service
will be stripped of other unreferenced methods.

Finally, this attempts to fix/clarify the behavior around when custom
options are included since they are also known extensions. If known
extensions are included in the filtered set AND one of the options
message types is part of the transitive dependency graph, all of the
relevant custom options will be included. Otherwise, if custom
options are included, ones actually referenced in options on the
elements in the transitive dependency graph will be present.

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Signed-off-by: dependabot[bot] <support@github.com>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

Release prepared for 1.11.0

Reminder: Update the changelog

Co-authored-by: joshcarp <joshcarp@users.noreply.github.com>
Co-authored-by: Joshua Carpeggiani <32605850+joshcarp@users.noreply.github.com>