feat(notification): add postgres queue

[mabdh]

Changes

• Add postgres queue
• Add dlq concept
  • with postgres, we don't have a dedicated dlq table for now
    • enqueuing to dlq means updating the status to failed
    • dequeueing dlq means republishing the failed messages that has not expired
  • failing message could be marked as retryable or non-retryable, if client got 429 rate limit or 500, it is retriable. If there is wrong config or client got 4xx, it is non-retriable.
• Add new cli
  • workers (workers mean another instance that run beside the server)
    • siren worker start notification_handler
    • siren worker start notification_dlq_handler
  • jobs (a task that runs once)
    • siren job run cleanup_queue - cleaning up messages that are published or stale in pending that already > specific threshold (default 7 days)
• Introduce a MaskableString
  • When logging secret/personal credentials, string will be masked with asterix (*)
• Add Pre and Post hook in receiver notification flow

[coveralls]

Pull Request Test Coverage Report for Build 3296791340

• 263 of 422 (62.32%) changed or added relevant lines in 21 files are covered.
• 2 unchanged lines in 1 file lost coverage.
• Overall coverage decreased (-2.5%) to 81.161%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
internal/store/postgres/subscription.go	7	9	77.78%
core/notification/service.go	21	24	87.5%
plugins/queues/postgresq/model.go	39	43	90.7%
plugins/receivers/slack/notification_service.go	29	33	87.88%
pkg/secret/secret.go	0	5	0.0%
core/notification/handler_option.go	0	6	0.0%
plugins/receivers/httpreceiver/notification_service.go	0	6	0.0%
plugins/receivers/pagerduty/notification_service.go	0	6	0.0%
plugins/queues/inmemory/queue.go	0	7	0.0%
core/notification/handler.go	22	46	47.83%

Files with Coverage Reduction	New Missed Lines	%
core/notification/handler_option.go	2	0%

Totals
Change from base Build 3224101768:	-2.5%
Covered Lines:	2951
Relevant Lines:	3636

---

💛 - Coveralls