Update Notify method to remove unused DumpType

DumpType is no more valid since there is there will be one
unique dump manager per dump type. So the implementation
need to call the right dump manager based on the path.
so removing the redundant option of passing dump type.

Signed-off-by: Dhruvaraj Subhashchandran <dhruvaraj@in.ibm.com>
Change-Id: I905a51f7c78b888b05412b0cb6a687b52b532609
diff --git a/xyz/openbmc_project/Dump/NewDump.interface.yaml b/xyz/openbmc_project/Dump/NewDump.interface.yaml
index 1e37990..6fa5809 100644
--- a/xyz/openbmc_project/Dump/NewDump.interface.yaml
+++ b/xyz/openbmc_project/Dump/NewDump.interface.yaml
@@ -13,10 +13,6 @@
       description: >
          Create a dump entry based on the parameters.
       parameters:
-       - name: DumpType
-         type: enum[self.DumpType]
-         description: >
-            Type of the dump
        - name: SourceDumpId
          type: uint32
          description: >
@@ -30,14 +26,4 @@
          description: >
             Size of the dump in bytes
       errors:
-        - xyz.openbmc_project.Common.Error.InternalFailure
         - xyz.openbmc_project.Dump.Create.Error.Disabled
-
-enumerations:
-    - name: DumpType
-      description:
-          Type of the dump
-      values:
-        - name: System
-          description: >
-              A dump created during a critical failure in the host.