[Visualize] User should be able to edit a broken visualization from a runtime field that has changed its type

[stratoula]

Describe the feature:
With the new runtime fields editor, the users can create new fields. Each time a field is created the user configures its type.

The user can create a visualization with this new field. But these fields are expected to change a lot. The users could for example change the fields' type (i.e. from double to string). This means that if the visualization is based on this field and a number type aggregation is applied, when the field changes from number to string the visualization should load with an error, allowing the user to edit the aggregations and fix the viz.

Now, the visualization appears on the listing but when the users try to edit it, it redirects them again to the listing page with a notification:

We also want the user to be able to edit the broken visualization from the dashboard too.

Note: If the new type is supported by the aggregation, the visualization works as expected.

[elasticmachine]

Pinging @elastic/kibana-app (Team:KibanaApp)

[mattkime]

@stratoula Can this issue be closed or is there additional work to be done?

[stratoula]

Same here @mattkime, closing it!