fix: move MaaSModel deprecation warning to module level after class definition (#2671)

- Prevents warning from being triggered on module import before the
  class is available for use

Author: myakove

ocp_resources/maa_s_model.py

@@ -7,13 +7,6 @@
 from ocp_resources.exceptions import MissingRequiredArgumentError
 from ocp_resources.resource import NamespacedResource
 
-warn(
-    "MaaSModel is deprecated and will be removed in a future release. "
-    "Please use `MaaSModelRef` from maas_model_ref.py instead.",
-    DeprecationWarning,
-    stacklevel=2,
-)
-
 
 class MaaSModel(NamespacedResource):
     """
@@ -50,3 +43,11 @@ def to_dict(self) -> None:
             _spec["modelRef"] = self.model_ref
 
     # End of generated code
+
+
+warn(
+    "MaaSModel is deprecated and will be removed in a future release. "
+    "Please use `MaaSModelRef` from maas_model_ref.py instead.",
+    DeprecationWarning,
+    stacklevel=2,
+)