Persist hooks to PG instead of Redis

[jerry-enebeli]

Describe the bug
Webhooks are being stored in Redis instead of a persistent database (PG). When Redis is restarted, all hooks created are lost, requiring them to be re-registered.

To Reproduce
Steps to reproduce the behavior:

1. Configure and register webhooks in core(using the pre or post hook endpoint)
2. Verify webhooks are working correctly
3. Restart the Redis instance
4. Attempt to use or view previously configured webhooks
5. Observe that all webhook configurations have been lost

Expected behavior
Webhooks should persist across Redis restarts. They should be stored in a persistent database (PG) so that restarting Redis does not result in data loss.

[shottah]

@jerry-enebeli I've done some digging to further evaluate this issue, and here's what I've found:

For local development upon the docker-compose.yml, we may solve this problem by mounting a persistence volume for the redis container:

services:
   redis:
   image: redis:7.2.4
   container_name: redis
      volumes:
      - redis_data:/data

volumes:
   redis_data:

For remote concerns, there are performance overheads which seem to me, to be weighed against the availability of a persistence mechanism, which I believe most major cloud providers already support.

[jerry-enebeli]

This is actually a good simple fix @shottah. Let's do it

Maybe later we can consider persisting to PG if other users still insist.

Thanks for looking into this 🙏