Drop (now) obsolete code paths

Since the data key is used per default now, these code paths (which also
(indirectly) implemented a check against the data key) became obsolete
now.

Signed-off-by: Jonas Brand (8R0WNI3) <[email protected]>

Author: 8R0WNI3

metadata.py

@@ -531,16 +531,6 @@ def reuse_discovery_date_if_possible(
             # resource-/package-version, so we must re-use its discovery date
             return old_metadata.discovery_date
 
-    elif new_metadata.type == odg.model.Datatype.DIKI_FINDING:
-        if (
-            new_metadata.data.get('provider_id') == old_metadata.data.get('provider_id')
-            and new_metadata.data.get('ruleset_id') == old_metadata.data.get('ruleset_id')
-            and new_metadata.data.get('rule_id') == old_metadata.data.get('rule_id')
-        ):
-            # found the same finding in existing entry, independent of the component-/
-            # resource-/ruleset-version, so we must re-use its discovery date
-            return old_metadata.discovery_date
-
     elif new_metadata.type == odg.model.Datatype.OSID_FINDING:
         if (
             new_metadata.data.get('osid').get('VERSION_ID')
@@ -551,11 +541,6 @@ def reuse_discovery_date_if_possible(
             # found the same version and name in existing entry, so we must re-use its discovery date
             return old_metadata.discovery_date
 
-    elif new_metadata.type == odg.model.Datatype.CRYPTO_FINDING:
-        if new_metadata.data_key == old_metadata.data_key:
-            # found the same finding in existing entry, so we must re-use its discovery date
-            return old_metadata.discovery_date
-
     if new_metadata.data_key == old_metadata.data_key:
         # found the same finding in existing entry, so we must re-use its discovery date
         return old_metadata.discovery_date