Create macros for throwing to avoid boilerplate code

[st0rmbtw]

This PR adds a new Throw.h file with the LLGL_THROW and LLGL_THROW_IF macros that work only if the LLGL_DEBUG or the LLGL_ENABLE_EXCEPTIONS are defined. So now LLGL can build with the -fno-exceptions compiler flag.

[LukasBanana]

I appreciate the cleanup work here. Another jobsite I wanted to pickup a long time ago and only did so incrementally. I'm fine with the new macro in the public interface for the few places with exceptions, like the container classes, but for all internal code, I'd prefer to stick with the LLGL_TRAP/LLGL_ASSERT macros as described in the comments.

[LukasBanana]

I think we can boil this down to just one new macro in the public interface. I left some more comments in the code changes.

[LukasBanana]

I found one last issue, the rest looks good. Once you updated this last bit, I'll merge tomorrow after the CIS build went through.

[LukasBanana]

I made some changes to the new exception throwing with e8d86d7. I hope you don't feel blindsided, I appreciate you getting the ball rolling on this matter. The behavior hasn't really changed, this will still throw exceptions if enabled, but in the case they are disabled, this provides a nice callstack to the standard error or breaks the debugger if one is attached. The only downside is that this change only accepts a handful of predefined exceptions such as std::invalid_argument, std::bad_cast etc., but I think that's fine since LLGL does handle any exceptions at all, it only throws them which allows the client programmer to exit the application more gracefully than with an abort.