Remove legacy options

`allow_duplicates` makes less sense when a project can have multiple schemas.
While conceptually useful, it will require careful reimplementation. One approach could be calls to `get_label()` passing both name and schema_id.
Either way this never really made sense on SDK since we don't enforce it on API side...

Author: anthony-chaudhary

sdk/diffgram/label/label_new.py

@@ -3,16 +3,12 @@
 
 def label_new(self,
               label: dict,
-              schema_id: int = None,
-              allow_duplicates: bool = False,
-              print_success: bool = True):
+              schema_id: int = None):
     """
 
     Arguments
         self,
         label_list, a list of label strings
-        ignore_duplicates, bool
-        print_success, bool
 
     Expects
 
@@ -29,14 +25,6 @@ def label_new(self,
     if not name:
         raise Exception("Please provide a key of name with a value of label")
     label['schema_id'] = schema_id
-    if allow_duplicates is False:
-
-        label_file_id = self.name_to_file_id.get(name, None)
-
-        if label_file_id:
-            warnings.warn("\n\n '" + name + "' label already exists and was skipped." + \
-                          "\n Set allow_duplicates = True to bypass this check. \n")
-            return
 
     endpoint = "/api/v1/project/" + self.project_string_id + \
                "/label/new"
@@ -46,8 +34,8 @@ def label_new(self,
 
     data = response.json()
     self.get_label_file_dict()
+
     if data["log"]["success"] == True:
-        if print_success is True:
-            print("New label success")
+        return
     else:
         raise Exception(data["log"]["error"])