[Bug] Issue with editor.destroy() and reinitialization

With GrapesJS 0.14.33 editor.destroy() was introduced (https://github.com/artf/grapesjs/commit/52f8bdf2e894de536d44c1699c1e18bbaf52488f), so that it is possible to initialize, destroy and reinitialize an editor.

Problem

After initializing, destroying, re-initializing, I am however experiencing exceptions when editing text-blocks with the default RTE. Today's destroy() eventually forgets to tear down s.th., so that it is possible to provoke the following:

Uncaught TypeError: Cannot read property 'body' of null
    at Object.getBody (grapes.js:24607)
    at Object.getWrapperEl (grapes.js:24616)
    at child.getCanvasWrapper (grapes.js:26883)
    at child.initialize (grapes.js:26842)
    at child.Backbone.View (grapes.js:5596)
    at child [as constructor] (grapes.js:6256)
    at new child (grapes.js:6256)
    at Object.get (grapes.js:26519)
    at Object.method (grapes.js:38111)
    at dispatch (grapes.js:19528)

or:

Uncaught TypeError: Cannot read property 'hasFocus' of null

Demo

Please find this fiddle for 0.14.33 including reproduction steps: https://jsfiddle.net/srkm18yu/

Related PRs and Issues

In my opinion PR #920 has already fixed part of this problem, but was not sufficient.

Other people have experienced the same issue in the past, especially when they are building SPAs, e.g. with Angular, since an SPA will reinitialize GrapesJS everytime the user navigates to page using a GrapesJS editor e.g. #1288.