STY: Applty ruff/pyupgrade rule UP006

UP006 Use `type` instead of `Type` for type annotation
UP006 Use `tuple` instead of `ty.Tuple` for type annotation

Author: DimitriPapadopoulos

nibabel/gifti/gifti.py

@@ -18,7 +18,7 @@
 import sys
 import warnings
 from copy import copy
-from typing import Type, cast
+from typing import cast
 
 import numpy as np
 
@@ -598,7 +598,7 @@ class GiftiImage(xml.XmlSerializable, SerializableImage):
     # The parser will in due course be a GiftiImageParser, but we can't set
     # that now, because it would result in a circular import.  We set it after
     # the class has been defined, at the end of the class definition.
-    parser: Type[xml.XmlParser]
+    parser: type[xml.XmlParser]
 
     def __init__(
         self,

nibabel/spatialimages.py

@@ -169,8 +169,8 @@ def set_data_dtype(self, dtype: npt.DTypeLike) -> None: ...
 @ty.runtime_checkable
 class SpatialProtocol(ty.Protocol):
     def get_data_dtype(self) -> np.dtype: ...
-    def get_data_shape(self) -> ty.Tuple[int, ...]: ...
-    def get_zooms(self) -> ty.Tuple[float, ...]: ...
+    def get_data_shape(self) -> tuple[int, ...]: ...
+    def get_zooms(self) -> tuple[float, ...]: ...
 
 
 class HeaderDataError(Exception):