Create properties/on_reindex_trigger methods to determine which components will be loaded on the portal

[maxsibilla]

In the current implementation of the Portal view pages (e.g. /dataset?uuid=....) various components get loaded after several seconds. The only issue with this is that the user is not aware that something is actively being loaded until it has finished and appears on the page. We can potentially get around this issue by indexing into Elasticsearch whether or not the entity will be displaying various components and on the portal we can check against though and display a Suspense component will we wait for data.

One prime example of this is the Vitessce visualization, which will not be displayed until we have a configuration returned from the Ingest API has there are scenarios where given the assay type, having a dataset and derived dataset in QA does not support a visualization. If we can somehow determine during index time if this entity will support a visualization we can show that component on page load and the visualization will load once that has been built.