fix: adjust mapping implementations

Revisit the justification for SSSOM mapping predicates. In some cases,
implementations shouldn't have been made at all. In others, logic is
needed to decide whether the value should be returned or not.
Specifically:

- Remove `schema:minValue` and `schema:maxValue` due to definitional
mismatches that break the exact match.
- Move `time:hasTRS` to the same level as `time:TimePosition` to follow
OWL time conventions.

Related to SSSOM changes in commit:
384fc5e

src/soso/strategies/eml.py

@@ -117,8 +117,6 @@ def get_variable_measured(self) -> Union[list, None]:
                 "measurementTechnique": get_methods(item),
                 "unitText": item.findtext(".//standardUnit")
                 or item.findtext(".//customUnit"),
-                "minValue": item.findtext(".//minimum"),
-                "maxValue": item.findtext(".//maximum"),
             }
             property_value = {
                 key: value for key, value in property_value.items() if value is not None
@@ -434,16 +432,16 @@ def convert_single_date_time_type(
             "@type": "time:Instant",
             "time:inTimePosition": {
                 "@type": "time:TimePosition",
+                "time:hasTRS": {
+                    "@type": "xsd:string",
+                    "value": single_date_time.findtext(".//timeScaleName"),
+                },
                 "time:numericPosition": {
                     "@type": "xsd:decimal",
                     "value": numeric_position,
                 },
             },
             "gstime:uncertainty": {"@type": "xsd:decimal", "value": uncertainty},
-            "time:hasTRS": {
-                "@type": "xsd:string",
-                "value": single_date_time.findtext(".//timeScaleName"),
-            },
         }
     return instant