bugfix(scorch): Prevent gameplay scorches from evicting map scorches

[stephanmeesters]

• Closes World Builder Bug: Fix the issue where placed scorch marks disappear after a certain amount is reached #364

Adds a separate instance of W3DScorch to be used only for "static" scorch marks placed on a map using World Builder. This fixes the issue that these static scorches eventually disappear during gameplay.

By using the separate instance of W3DScorch, with its own GPU buffers, the static scorches will not have much performance impact: the buffer does not change often and is cheap to draw. The exception is changes to terrain geometry or changes to the map lighting, which invalidates all of the scorch buffers.

Deduplication of static scorches is disabled, as dedup checking adds to map loading time (especially if we were to increase the max nr of scorches later), and we can trust map makers to place the scorch marks correctly.

Todo

• Rebase after bugfix(scorch): Update scorch texture mip quality when changing texture quality setting #3119

[Caball009]

Nice fix.

I did notice during testing, however, that at some point the game refuses to render scorch marks. You can reproduce this by putting down 3 scorch marks of size 256 with the world builder. The third one isn't rendered; not in the world builder nor in game. This is retail behavior and not introduced by this PR, but for the bug fix to be more effective it'd be nice if that's fixed as well.

[stephanmeesters]

I did notice during testing, however, that at some point the game refuses to render scorch marks.

Yes I agree this should be fixed too, this is the issue described in #179, where we run into a vertex/index buffer limit. This buffer max size can be increased to the 16 bit index limit to alleviate the issue somewhat in the short term.