LibJS+LibWeb: Replace GlobalObject with Realm in object constructors

No functional changes - we can still very easily get to the global
object via `Realm::global_object()`. This is in preparation of moving
the intrinsics to the realm and no longer having to pass a global
object when allocating any object.
In a few (now, and many more in subsequent commits) places we get a
realm using `GlobalObject::associated_realm()`, this is intended to be
temporary. For example, create() functions will later receive the same
treatment and are passed a realm instead of a global object.

Userland/Libraries/LibJS/Runtime/AsyncFunctionConstructor.cpp

@@ -12,8 +12,8 @@
 
 namespace JS {
 
-AsyncFunctionConstructor::AsyncFunctionConstructor(GlobalObject& global_object)
-    : NativeFunction(vm().names.AsyncFunction.as_string(), *global_object.function_constructor())
+AsyncFunctionConstructor::AsyncFunctionConstructor(Realm& realm)
+    : NativeFunction(vm().names.AsyncFunction.as_string(), *realm.global_object().function_constructor())
 {
 }