🔧 Add an explicit Chronographer config

[webknjaz]

In particular, this allows setting up hints for leading the
contributors to the docs that explain the changelog fragments
expectations. This allows having the preferences documented as code.

The patch also sets the label for ignoring the change note
requirement.

[webknjaz]

@pradyunsg feel free to edit out the undesired stuff. This adds configs for some of your earlier requests.

[pfmoore]

Can someone provide some background on what this is, and how it affects the project? The PR doesn't include any changes to the docs - does that mean the development workflow is unaffected?

[webknjaz]

@pfmoore it's a replacement for the towncrier fragment check implemented as a GitHub App as opposed to a GHA workflow. It's a partial derivative of browntruck. This is the config for said app. It's been in use in various GH orgs since 2019 but I originally started the project because Pradyun asked me to explore refactoring the legacy webhook based integration. We got back to checking how ready the app was once in a while, Pradyun asked for more toggles and they are finally in place.

The earlier proposal was here: #6475.

Your workflow will not change thanks to the recent updates allowing to have a custom label name but the check result may look a bit different.
The GHA workflow is still in place to allow some time for comparison — so you'll see two checks being reported until it's removed. This will let us see if there's anything else people are missing from this integration.
Also, the GitHub App can be suspended at any time in the repo/org settings. This is what Pradyun did when we first installed it but realized that a few more changes were needed.

I've just retriggered the check on another PR, you can see it here: #11861.

[pfmoore]

Cool, thanks for the explanation!