NORSPEC-198, NORSPEC-176, NORSPEC-106, NORSPEC-202 et al -- Material matrix testing based overhaul WIP

Reviewed by Graham

NORSPEC-182 do not add 'Use Texture' menu items in XML to avoid accidental appearance in menu 1st time

NORSPEC-189 throw caution to the wind and avoid using getVolume() check which has deleterious effects on materials rendering

NORSPEC-96 NORSPEC-189 another attempt at planar stretch across all 3 channels and make the materials CB use a UUID instead of this pointer for safety

NORSPEC-210 fix issues with the map used to store TE-specific registrations which was only invoking the CB for the last TE on log-in by replacing std::map with boost::unordered_map

NORSPEC-192 fix more incorrect batching, fix bug in reflecting normal map state in build tool, and protect against callback crashes when switching regions

Introduce LLCoros::setStackSize(), with a compile-time default value we hope
we never have to use. Make LLAppViewer call it with the value of the new
settings variable CoroutineStackSize as soon as we've read settings files.
(While we're at it, notify interested parties that we've read settings files.)
Give CoroutineStackSize a default value four times the previous default stack
size. Make LLCoros::launch() pass the saved stack size to each new coroutine
instance.
Re-enable lleventcoro integration test. Use LLSDMap() construct rather than
LLSD::insert(), which used to return the modified object but is now void.

NORSPEC-193 NORSPEC-161 add new batch break criterion to CompareBatchBreakerModified and add shortcut for materials info dump

NORSPEC-186 clamp norm/spec map rotations to 0-360 until we can fix the server side issue with negative rotations

NORSPEC-96 tweak fix to follow clone/modify/re-apply pattern from build tool to avoid changing objects sharing a material

NORSPEC-200 fix regression from 188 fix caused by not having enough bits to store SHINY_TEXTURE in the TEs bitfield

NORSPEC-188 avoid removing 'Use Texture' item when cancelling from picker back to having prev texture

Quieten down writing to fmod.log - only write errors - speculate this is related to audio stutter/frame stalls