fix: self hosted replay storage access

[pauldambra]

I promise I'm not working... but I am doing lots of waiting so I set up a linode with self-hosted posthog and pointed my blog at it

Replay does not work OOTB at all. Something has broken at some point or folk aren't reporting all their problems.

web, worker, and plugins deployment all need to be able to access object storage in order for replay features to work

but they can't so replay only works while data is buffered in redis - no bueno

this provides the hard coded auth/config that will allow access to minio

with this config in place my OOTB install started working

(I don't know if this will break things for folk who have set config to support e.g. their own S3 access 🤷)

[pauldambra]

@daibhin creating this so I don't lose track of it, probably need support from someone with docker chops to figure out if this is a bad way to fix things since some folk must have already overridden this but the OOTB experience is no good at all right now

[posthog-bot]

This PR hasn't seen activity in a week! Should it be merged, closed, or further worked on? If you want to keep it open, post a comment or remove the stale label – otherwise this will be closed in another week. If you want to permanentely keep it open, use the waiting label.