Config validation error

[whilefoo]

Resolves #680

Example:
ubiquity-whilefoo@b74601f#comments
ubiquity-whilefoo@c8e02c0#comments

It was kinda hard to log config errors because if the config was invalid, I also didn't have Supabase keys which the logger needs to write logs to database, so I had to write additional fallbacks

[netlify]

✅ Deploy Preview for ubiquibot-staging ready!

Name	Link
🔨 Latest commit	3914532
🔍 Latest deploy log	https://app.netlify.com/sites/ubiquibot-staging/deploys/65001875ab123800087f6c8c
😎 Deploy Preview	https://deploy-preview-684--ubiquibot-staging.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[0x4007]

First one is great. Second one is vague is there anything you can do to improve that type of message?

[whilefoo]

I improved the message:
ubiquity-whilefoo@386a772#comments

[web4er]

It would be nice to get the name additional properties in console logs and supabase logs.

biquiBot Error: Invalid repo config: data must NOT have additional properties undefined error ubiquibot web4erOrg undefined undefined

The bot didn't add comment here on wrong config.
web4erOrg@e556157

I have only price-multiplier and issue-creator-multiplier in my org config. If I add only price-multiplier in repo config, this shows up in console log and supabase log, but nothing in commit comments.

UbiquiBot Error: Invalid repo config: data must have required property 'issue-creator-multiplier' undefined error ubiquibot web4erOrg undefined undefined

[whilefoo]

It would be nice to get the name additional properties in console logs and supabase logs.

Added

The bot didn't add comment here on wrong config.
web4erOrg@e556157

This happened because the config on development was invalid, so you pushed the change, the bot tried to load the current config but it's invalid so it stops. I modified the code to run validateConfigChange even if config load fails.

[0xcodercrane]

It looks like you should merge the development branch into your local config-validation-error branch @whilefoo