core/aggsigdb: refactor concurrent access issue in test

[gsora]

Use sync.Map with a thin abstraction for data and keys by duty maps.

category: bug
ticket: #1867

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (main@f88ef52). Click here to learn what that means.
Patch coverage: 87.75% of modified lines in pull request are covered.

❗ Current head 1825cc8 differs from pull request most recent head 8e0f37d. Consider uploading reports for the commit 8e0f37d to get more accurate results

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1950   +/-   ##
=======================================
  Coverage        ?   55.45%           
=======================================
  Files           ?      174           
  Lines           ?    22344           
  Branches        ?        0           
=======================================
  Hits            ?    12391           
  Misses          ?     8373           
  Partials        ?     1580           

Impacted Files	Coverage Δ
core/aggsigdb/memory.go	84.57% <87.75%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[corverroos]

aggsigdb has a central goroutine that accesses all state, so sycnronisation not required. If race is due to tests, rather use callback functions called by that central goroutine.

[gsora]

Will fix the test instead.

[gsora]

Reopened with a new approach.

LMK what you think @corverroos.