Expore improvements to minimap rendering performance

[Tyriar]

Currently we use putImageData to redraw the entire minimap each frame, we should explore keeping the source of truth of the image in the canvas and printing diffs to minimize the amount of rendering.

[Tyriar]

Not sure if there will be time for this in September (it's on the iteration plan though).

[alexdima]

I have pushed an optimization where the dirtyY and dirtyHeight arguments of putImageData are exercised to reduce in many cases how much painting is done.

@Tyriar I leave it up to you to explore further optimizations.

[vscodebot]

This iteration we focus on issue grooming. This issue is being closed to keep the number of issues in our inbox on a manageable level, we are closing issues that are not going to be addressed in the foreseeable future: We look at the number of votes the issue has received and the number of duplicate issues filed. More details here. If you disagree and feel that this issue is crucial: We are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding and happy coding!