Move webhooks from config to the database

[TurtIeSocks]

As title. Move webhook settings from the config to the database and add an API endpoint to hot reload.

[jfberry]

Why?

[lenisko]

Hmm... I think it's a good idea, but worth nothing that restarting Golbat is not troublesome at all.

[jfberry]

...and there is no user interface config for golbat, and I'm not sure there would ever need to be
plus how often do you change webhook destinations?

[TurtIeSocks]

Ease of setting up, troubleshooting, changing, particularly for dev use.

There isn't a UI, yet. But I see no reason why there shouldn't be some Golbat pages on a certain admin project, particularly if it were to receive it's own server, since it's already making calls to Golbat.

[lenisko]

I'm always a fan of highly tunnable software. Whole config (aside some critical parts) could be hot-reload through API. Having API, creating UI ang even serving it even via Gin (to make it easy) is easy as pie.

Though! In current state, it would make a small impact, as we don't have enough tunnable switches/options and restart is taking ~3seconds (which is the amount of lost data as well).