* Revert "fix(vroom): Explicitly set PROFILES_DIR for upcoming change (#3759)"
This reverts commit e07445d6be41793165316a3e077ebec343740530.
It also very importantly changes where we mount the profiles volume which fixes the issue. Our theory is as follows:
1. Vroom Dockerfile had a line doing `mkdirp /var/lib/sentry-profiles` at image build time. This makes the directory owned by `root`
2. When we mount over that directory, and change permissions we can store the permissions changes _in_ the directory but not the directory itself
3. So when we start the vroom image with the new mount, the contents are owned by `vroom` but the main directory is still owned by `root`. This is also why [this approach](a23a4e3952) worked as the entrypoint script did this at the start of every container instance.
---------
Co-authored-by: Burak Yigit Kaya <byk@sentry.io>
* Introduce patches with external kafka
* Fix pre-commit hooks
* Patch relay config file
* Documentation for patches stuff
* Provide more helpful information for Docker Compose Override file
* Fix grep command
* ref: rename to 'optional-modifications'
* chore(pre-commit): exclude .patch extension
* chore(pre-commit): escape backslash
* chore(pre-commit): put exclude field on hooks
* chore(pre-commit): put exclude field on top level
Based on https://pre-commit.com/#top_level-exclude
* chore(pre-commit): move to even more top level
