These were added as part of understanding the code, commiting in case they might be useful for others as well.

This is what probot actually uses to identify the org, so it should probably be there in the fixture.

When `sender.type` is bot, the change is skipped. This led to the test checking for changes on this event failing.

This seems to me to be the best way for logs to show up in a useful fashion when running tests.

This is needed for the test to be able to check that it was called.

Also adds support for ovveriding the filter list in `Diffable.sync`.
This is needed for milestones to work correctly. However, it should be tested well to ensure it does not break anything else.

I believe this change makes the logic easier to follow, especially not returning data that does not need to be returned.

This change should give the exact same result, except moving the `else`-block within the try/catch (and I don't see why that is bad).

The refactor makes it easier to understand the difference in logic with and without a present `repoConfig` by only having the actual alternate action within the if/else and keeping the bit that always happen outside the if/else.

Linting failed in deploymentConfig.js due to the static fields. Eslint supports this from ecmaVersion 13.

The full test suite failed because it tried to lint the tests, while the running linter did not do the same. Enabling linting gave errors due to jest having undef stuff, but overriding these files for jest env keeps the linting without these errors.