Generate the configuration.md file automatically on changes to the configuration code.

[t4lz]

I think it would be nicest if we could have the patch automatically pushed to main after a commit with changes to the config is merged into main.

If we're afraid of automatically pushing to main, we could maybe push into a PR's branch instead, once it's created and has changes to the config crate.

The weakest option would be to just regenerate that file and require it not to be different, like we do with the json schema, forcing contributors to regenerate that file manually when needed.

Depending on what strategy we choose, this might be combined with metalbear-co/mirrord.dev#207.

[infiniteregrets]

pushing to main doesnt sound good, id rather think of doing a check on each pr if mirrord/config/ has been changed and the job should fail. this weak check imo is more flexible... and perhaps having a pre commit hook makes sense here?