Fix EGL error code reporting in GLException messages

[NamtarR]

Problem

In all cases when GLException is thrown, eglGetError() is being called twice - once for the exception constructor and once for the error message. Since eglGetError() clears the error state after being called, the second call always returns EGL_SUCCESS instead of the actual error code. While debugging locally, it is still possible to retrieve the initial error code from the exception object, but it gets completely lost when the exception is reported to crash reporting tools like Crashlytics. This unintentional masking of the real error makes debugging such cases more difficult than it should be. There are several issues in livekit-android with the same problem as well.

Solution

Extract a throwEglException helper method that accepts the error code as a parameter. Call eglGetError() only once at each call site and pass the result to throwEglException.