X Correct tac in NR peer

TAC ranges are different in between LTE and NR.

software/ors-amarisoft/cell/nr/input-schema.json

@@ -75,5 +75,13 @@
       "description": "Range 0 to 837 for PRACH format up to 3, 0 to 137 otherwise. prach-RootSequenceIndex parameter. It must be different for each neighbour cell operating on the same frequency and sharing the same PRACH configuration.",
       "default": 1
     }
+  },
+
+  "$defs": {
+    "tac": {
+      "title": "Tracking Area Code",
+      "description": "Integer (range 0 to 16777215)",
+      "type": "number"
+    }
   }
 }

software/ors-amarisoft/instance-enb-input-schema.json

@@ -106,9 +106,7 @@
               "type": "string"
             },
             "tac": {
-              "title": "Tracking Area Code",
-              "description": "Integer (range 0 to 16777215)",
-              "type": "number"
+              "$ref": "cell/nr/input-schema.json#/$defs/tac"
             },
             "ranac": {
               "title": "Optional integer (range 0 to 255)",

software/ors-amarisoft/peer/cell/nr/input-schema.json

@@ -38,6 +38,6 @@
     "ssb_nr_arfcn": { "$ref": "../../../cell/nr/input-schema.json#/properties/ssb_nr_arfcn" },
     "ul_nr_arfcn":  { "$ref": "../../../cell/nr/input-schema.json#/properties/ul_nr_arfcn" },
     "pci":          { "$ref": "../../../cell/nr/input-schema.json#/properties/pci" },
-    "tac":          { "$ref": "../../../cell/lte/input-schema.json#/properties/tac" }
+    "tac":          { "$ref": "../../../cell/nr/input-schema.json#/$defs/tac" }
   }
 }