feat: Queuing; Refactor Extractors to Tasks; refactor MemoryStore interface

[danielchalef]

• Add SQL TaskQueue using Watermill
• Refactor Extractors to new Task queue model
• Refactor MemoryStore Interfaces as precursor to refactoring MemoryStore
• Code cleanup

[moltar]

@danielchalef wow, looks like a ton of work went into this one. I am not familiar with Go yet to grok all the changes. But does this require any migrations? Or does Go code migrate implicitly when you start the service? Are there any docs for this change? Thanks!!

[danielchalef]

@moltar No migrations were necessary. The functional router "Task" schemas remained the same as the prior "Extractor" tasks. The message queue framework I used automatically generates schemas for each handler. Since this change was an internal shift from an observer model using Go channels as queues, to a SQL-based message queue architecture, I've not prioritized documenting it! I will get around to doing so sometime soon!

[moltar]

Alright thank you for explaining. I was only looking for any end user docs, but sounds like none needed.

I was thinking in the context of applying database migrations manually for this change. But given that it's under the hood implementation detail then is all good.