fix: remove forced rerender from mutator

[BeksOmega]

The basics

• I branched from develop
• My pull request is against develop
• My code follows the style guide
• I ran npm run format and npm run lint

The details

Resolves

Fixes #3511
Fixes #6953
Work on #4288

Proposed Changes

Removes the batch rendering from the mutator logic - since we now have actual batch rendering that doesn't rely on mangling the rendered property!

Reason for Changes

Code simplification.

Test Coverage

Manually tested that #4175 and #3458 do not reproduce.

Tested that mutating continues to work.

Documentation

N/A

Additional Information

While I do trust this code, I don't trust it enough to put it into the imminently approaching release. So I'm going to put this up as a draft.

[maribethb]

Fixes #6953 correct?

[BeksOmega]

Fixes #6953 correct?

Editted PR description!

[EricAlm]

Sorry, what should I do to have the solution to #6953 ?

[cpcallen]

While I do trust this code, I don't trust it enough to put it into the imminently approaching release. So I'm going to put this up as a draft.

I applaud this instinct, but it looks like in this particular case you should have had more faith in your coding!

[cpcallen]

Sorry, what should I do to have the solution to #6953 ?

The easiest thing is to wait for the next release of Blockly.

If this (annoying but largely cosmetic) bug can't wait, you can build Blockly yourself from the develop branch. Unfortunately the "Building Blockly" instructions on our website are out-of-date (they'll get fixed soon—that's pretty much the next item on my to-do list) but for now if you clone the google/blockly repository and then npm install && npm run package to build Blockly. After that, if you (cd dist && npm link) within Blockly, then npm link blockly in your own project, your project will (temporarily) be linked to the version of Blockly built in dist/ (instead of the version obtained from the NPM registry).