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.

1 files changed, 2 insertions, 2 deletions

diff --git a/Userland/Libraries/LibJS/Runtime/Intl/PluralRulesConstructor.cpp b/Userland/Libraries/LibJS/Runtime/Intl/PluralRulesConstructor.cpp
index 8d732ecf89..4ec5c32552 100644
--- a/Userland/Libraries/LibJS/Runtime/Intl/PluralRulesConstructor.cpp
+++ b/Userland/Libraries/LibJS/Runtime/Intl/PluralRulesConstructor.cpp
@@ -16,8 +16,8 @@
 namespace JS::Intl {
 
 // 16.1 The Intl.PluralRules Constructor, https://tc39.es/ecma402/#sec-intl-pluralrules-constructor
-PluralRulesConstructor::PluralRulesConstructor(GlobalObject& global_object)
-    : NativeFunction(vm().names.PluralRules.as_string(), *global_object.function_prototype())
+PluralRulesConstructor::PluralRulesConstructor(Realm& realm)
+    : NativeFunction(vm().names.PluralRules.as_string(), *realm.global_object().function_prototype())
 {
 }