Although in the technical design document we opted to move a number of the customizable parts of rendering fields and field types to the consumer of the diagramming package, we have found that that introduces more complexity when react flow needs to render the respective field or node. In addition to this complexity, and non-serializable state, it also can cause unintended re-renders, which will hinder performance and cause flashes.

This ticket involves adding new callback functions to the diagramming library, which, when supplied, will render related actions for fields and nodes. Let's then remove the actions and custom render functions we've added. Down the line if we need to add custom rendering passed by a consumer we should instead have it be something that's supplied as a generic function which we can then use with react context in the location that react flow renders as to avoid passing around components in field or node data.