Prompt user to report a bug if graph becomes unrenderable due to an act of tooling

The graph can fail to render due to a type error, or outright crash. If this happens while a user is interacting with WYSIWYG tooling (i.e. the graph isn't open), we should consider this a bug because the tooling broke the graph. In this situation, we should indicate to users that this situation isn't supposed to happen, and request they report the bug.

To prevent users from being prompted to report bugs arising from noodling around in the graph, even if they subsequently close the graph and Ctrl+Z their way back to the broken graph, we should store if the graph was open or closed during the document history snapshot. We could also open the graph for the user automatically if they undo/redo to a point when the graph was invalid and that node graph was open at that time. If so, it should also close the graph if the user undoes/redoes past that point and returns to a valid graph, without having interacted with the automatically-opened graph.

Commencez par localiser les outils de graphes WYSIWYG et la gestion des snapshots de l’historique du document décrits dans l’issue. Suivez la manière dont les graphes invalides et l’état d’undo/redo sont représentés ; done doit distinguer les échecs causés par les outils de l’édition du graphe, préserver le fait que le graphe était ouvert et appliquer le reporting demandé ainsi que le comportement automatique d’ouverture/fermeture.

Rédigé par le modèle d'indexation à partir du texte de l'issue.