fix: model-config ES errors

[mwdchang]

Summary

This fixes two things

• ES errors when fetching model-configurations via model id cause by non-existing field and typos
• Do not refresh and fetch a listing of model-configurations a the model-configuration node when the input port is connected, the interaction paradigm has changed and handled in the drilldown instead

The resulting ES error:

{"error":{"root_cause":[{"type":"query_shard_exception","reason":"No mapping found for [timestamp] in order to sort on","index_uuid":"Sgoz2pkbQb2bqF4HlTEW7A","index":"tds_modelconfiguration_tera_2.0"}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"tds_modelconfiguration_tera_2.0","node":"vjctqqzaQJSQvb-8Uwnlcg","reason":{"type":"query_shard_exception","reason":"No mapping found for [timestamp] in order to sort on","index_uuid":"Sgoz2pkbQb2bqF4HlTEW7A","index":"tds_modelconfiguration_tera_2.0"}}]},"status":400}

Testing

• ES errors can be tested through GET /models/:id/model-configurations
• Attach a model to model-configuration operator will not cause ES to error out

[YohannParis]

Perfection!