Fix: Update config.yml

[isabelle-dr]

Tiny fixes to the welcome bot messages.

Please make sure these boxes are checked before submitting your pull request - thanks!

• [ ] Run the unit tests with gradle test to make sure you didn't break anything
• Format the title like "feat: [new feature short description]". Title must follow the Conventional Commit Specification(https://www.conventionalcommits.org/en/v1.0.0/).
• Linked all relevant issues
• [ ] Include screenshot(s) showing how this pull request works and fixes the issue(s)

[github-actions]

Thank you for this contribution! 🍰✨🦄

Information about source corruption

1 out of 1335 sources are corrupted.
The following sources are corrupted:

• de-unknown-ulmer-eisenbahnfreunde-gtfs-1081

Acceptance test details

The changes in this pull request did not trigger any new errors on known GTFS datasets from the MobilityDatabase.
Download the full acceptance test report for commit 7c55c2e here (report will disappear after 90 days).

[maximearmstrong]

LGTM! Thanks @isabelle-dr

[isabelle-dr]

@maximearmstrong do you know what happened here? The test failed
https://github.com/MobilityData/gtfs-validator/runs/7469587766?check_suite_focus=true#step:9:424

[maximearmstrong]

Yes, there is an out-of-memory error occurring when validating Colectivos (Buenos Aires, Argentina) in the End to end big workflow:
Error: Process completed with exit code 137.

It seems the dataset is too big, but since it's the last one validated in the workflow, maybe we are using all the memory available in the virtual machine (see vm resources here).

This is not related to #1206, but it's part of the "are end-to-end workflows working correctly?" conversation. We experience a lot of problems with them lately, it would be good to investigate their behavior.

[isabelle-dr]

Okay, merging this PR since the test failure seems unrelated. Thank you @maximearmstrong!