Revert "chore: update dependencies (#89)"

[abnegate]

Reverts the dependency bump merged as 8a93696 (#89), so the weekly automation has work to redo on a clean manual run once #90 lands.

The bump itself was correct — every pin moved with its companion reference, and the resulting image built and reported the right extension versions. It is being reverted only so the run can be repeated end to end, not because the content was wrong.

Restores:

	reverted to
brotli	0.20.0 / 45faa7966ddc
mongodb	2.3.3 / 06be1f01bb4c
protobuf	5.35.1 / 7ab8cd62e8b7
zstd	0.17.0 / 1774622c25aa

Order of operations

1. Merge (fix): accept generated notes on the draft release #90 — without it the release step fails again at the same place.
2. Merge this.
3. Clear the leftovers from the failed run (below).
4. Dispatch Update Dependencies.

Leftovers that must be cleared first

The failed run got as far as tagging and drafting before it died, so two artefacts survive and will confuse the retry:

• tag 2.0.1 → 8a93696 (the commit this PR reverts)
• draft release 374170913 for 2.0.1

Both point at a commit that will no longer be main's tip. Left in place, the next run either resumes recovery against the reverted commit or drafts against a stale tag. I have not deleted either — that is destructive and yours to call.

[greptile-apps]

Greptile Summary

This PR intentionally restores the previous brotli, MongoDB, protobuf, and zstd source pins so dependency-update automation can be rerun cleanly after its release workflow is fixed.

• Reverts four extension versions together with their immutable commit or checksum references.
• Leaves all other extension pins and Docker build behavior unchanged.

Confidence Score: 5/5

The code change appears safe to merge, with the separately documented stale tag and draft-release cleanup remaining an operational prerequisite for rerunning automation.

The reverted values preserve each version’s companion immutable reference, restore a prior known-good configuration, and do not conflict with repository validation or a documented minimum-version contract.

Important Files Changed

Filename	Overview
Dockerfile	Restores four previously used extension version/reference pairs; no actionable inconsistency or compatibility failure was identified.

_{Reviews (1): Last reviewed commit: "Revert "chore: update dependencies (#89)..." | Re-trigger Greptile}