Collaboration ElasticSearch Mapping Not Always Created Correctly

Most of the failures with this MR are related to the collaboration field not always being searchable by ElasticSearch. This failure is intermittent and depends on whether the ElasticSearch Mapping that gets created has the collaborationId field or not. If it does have the mapping, then the test passes. If it does not, then ElasticSearch will disregard the collaborationId field and return an apparently incorrect result (all records will be in System-of-Record, instead of some correctly namespaced as expected for collaboration workspace). For reference, Indexer's specific ADR is available here, with related ADRs for Search service and Storage service.

I started on a preliminary MR to diagnose (and hopefully fix) these issues, but am not certain about the best way of implementing this on Indexer service and am handing it off. I have also created this MR that should be reverted when the ElasticSearch Mapping is consistently aware of the collaborationId field.