Use a separate orchestrator for each namespace

[awrichar]

Changed in this PR:

• Namespace manager is now the root manager in the system
• There is a separate orchestrator for each namespace, along with a separate instance of (almost) every manager
• Config for including different plugins in each namespace is now honored
• Each plugin supports multiple listeners, and each listener function (mostly on event manager) will filter out events from just the one namespace to which it's assigned

Broken in this PR:

• You cannot have multiple namespaces that point at the same blockchain FireFly contract, or the same token pool. They will end up sharing an event stream and therefore only one of them will process events. Fixing this will require splitting a lot of the contract/event stream logic out of the blockchain plugins into a new per-namespace component.
• Performance of event processing degrades almost linearly with the number of created namespaces, due to the fact that most events are fired to all instances of the event manager and then examined in order to process or ignore them. In the future, we can push namespace knowledge down into lower layers to make this decision earlier and avoid this extra overhead.
• SPI route for "get all operations" is moved from /operations to /namespaces/{ns}/operations, which represents a breaking change against FFTM.

Also includes the changes from #856.

[codecov-commenter]

Codecov Report

Merging #855 (f7559c9) into main (15c8802) will decrease coverage by 0.02%.
The diff coverage is 99.51%.

❗ Current head f7559c9 differs from pull request most recent head f96daef. Consider uploading reports for the commit f96daef to get more accurate results

@@            Coverage Diff             @@
##             main     #855      +/-   ##
==========================================
- Coverage   99.98%   99.96%   -0.03%     
==========================================
  Files         299      300       +1     
  Lines       19523    19510      -13     
==========================================
- Hits        19521    19504      -17     
- Misses          1        5       +4     
  Partials        1        1              

Impacted Files	Coverage Δ
internal/apiserver/route_spi_get_ops.go	100.00% <ø> (ø)
internal/database/sqlcommon/namespace_sql.go	100.00% <ø> (ø)
internal/events/subscription_manager.go	100.00% <ø> (ø)
internal/metrics/metrics.go	100.00% <ø> (ø)
internal/identity/tbd/tbd.go	90.00% <50.00%> (-10.00%)	⬇️
internal/sharedstorage/ipfs/ipfs.go	97.50% <50.00%> (-2.50%)	⬇️
internal/tokens/fftokens/fftokens.go	99.52% <90.47%> (-0.48%)	⬇️
cmd/firefly.go	100.00% <100.00%> (ø)
internal/apiserver/route_get_namespace.go	100.00% <100.00%> (ø)
internal/apiserver/route_get_namespaces.go	100.00% <100.00%> (ø)
... and 49 more

---

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 15c8802...f96daef. Read the comment docs.

[awrichar]

I don't love this testing workaround, but I was struggling to find a better way.

[peterbroadhurst]

Should we not do this in this PR? Having a broken endpoint seems bad, and it should be fine to make it namespaces/{ns}/operations

[peterbroadhurst]

(We still need the operations/{nsopid} routes for GET and PATCH, where the namespace is embedded into the ID)

[awrichar]

Yep that works - I can replace that route. Just wanted to get your feedback on how to spell it in the context of the other SPI routes and the usage by FFTM.

[peterbroadhurst]

Thanks for calling out all the considerations for where we end up after this (big!) step forwards. Looks good. I did have a couple of very minor comments along the way to review before merge.