fix: tenant s3 credentials fixes and refactor

[itslenny]

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

Cache does not invalidate on database update/delete and s3 credential count always returns 0

What is the new behavior?

Cache is invalidated on database update/delete, credential count returns correct value, credentials limited to 50, cleaner architecture, improved test coverage

Changes

• migration to use correct cache key in pg_notify cache invalidation
• fix s3 credentials count, was always returning 0 (and allowing creation of > 50 credentials)
• check for valid uuid on delete credential endpoint (used to throw 500 on insert)
• refactor s3 credentials into manager pattern similar to jwks
• add test coverage
• updated add jwk endpoint to use 201 to match existing s3 credentials
• some easy eslint fixes that caught my attention

[coveralls]

Pull Request Test Coverage Report for Build 14404300513

Details

• 218 of 223 (97.76%) changed or added relevant lines in 15 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage increased (+0.7%) to 78.398%

---

Changes Missing Coverage	Covered Lines	Changed/Added Lines	%
src/http/plugins/jwt.ts	2	3	66.67%
src/http/plugins/signature-v4.ts	1	2	50.0%
src/internal/database/tenant.ts	11	12	91.67%
src/internal/streams/monitor.ts	0	1	0.0%
src/storage/events/webhook.ts	0	1	0.0%

Totals
Change from base Build 14399279405:	0.7%
Covered Lines:	16610
Relevant Lines:	21027

---

💛 - Coveralls