Spike: Record Contribution: Analyze Re-Index job implementation usage in mod-inventory-storage

Purpose/Overview:

Open question: should the same topic but new event type be used, or does dedicated topic fit better? (RA: i'm not a fan of making separate topics per every case but here it seems to be safer in order not to impact on other consumers... though for Kafka itself and its clients it should not be a problem to filter out events with unknown event type...). One more note: having 2 topics allows to manage them - e.g., process full contribution first, and after that only continue with regular contribution

Open question: does it make sense to implement an mod-inventory-storage endpoint accepting a condition(-s) for filtering out events?

 Acceptance criteria:

• development team has understanding what should be implemented to start or cancel re-iteration process in mod-inventory-storage
• any updates required to mod-inventory-storage are identified