[gl] Improved logging options in expo-gl (#7550)

# Why

#7502 reminded me that we should have better logging/debugging options for `expo-gl` as we don't log anything by default and, most importantly, we don't log any errors like all web browsers do.

# How

- Removed `gl.enableLogging` -> it isn't a part of WebGL specification so imho it should somehow indicate itself as Expo-specific. We don't need to deprecate it first as it wasn't documented.
- Added `gl.__expoSetLogging` method which receives bitwise enum `GLLoggingOption` (check out tsdoc comments for more details).
- Moved the code responsible for logging to separate file (called `GLUtils`, because I believe we can put more stuff there soon).
- Slightly improved how WebGL objects are being stringified by us. Some of them were being logged as `[object Object]`.
- Added a few missing TypeScript property declarations.

# Test Plan

Tested by adding `gl.__expoSetLogging` method call to NCL example and playing with some custom `GLLoggingOption` values.

packages/expo-gl/CHANGELOG.md

@@ -6,6 +6,8 @@
 
 ### 🎉 New features
 
+- Improved logging and added some more logging options. ([#7550](https://github.com/expo/expo/pull/7550) by [@tsapeta](https://github.com/tsapeta))
+
 ### 🐛 Bug fixes
 
 - Fix depth/stencil buffers not working correctly with `three.js`. ([#7543](https://github.com/expo/expo/pull/7543) by [@tsapeta](https://github.com/tsapeta))