nimble/host: Change services pkg init priorities

Let's define following init priorities for service packages:
- 301 for GAP
- 302 for GATT
- 303 for other services

This will make services register in this order to upon discovery we'll
always have GAP first, then GATT and other services. Note that this
particular order is not required by is probably used by virtually any
device as it makes sense to have mandatory services first.

X-Original-Commit: a0c805462cc54167a339a9d62a265dbc7cb8dcf0

nimble/host/services/ans/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_ans_init: 300
+    ble_svc_ans_init: 303

nimble/host/services/gap/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_gap_init: 300
+    ble_svc_gap_init: 301

nimble/host/services/gatt/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_gatt_init: 300
+    ble_svc_gatt_init: 302

nimble/host/services/ias/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_ias_init: 300
+    ble_svc_ias_init: 303

nimble/host/services/lls/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_lls_init: 300
+    ble_svc_lls_init: 303

nimble/host/services/tps/pkg.yml

@@ -31,4 +31,4 @@ pkg.deps:
     - net/nimble/host
 
 pkg.init:
-    ble_svc_tps_init: 300
+    ble_svc_tps_init: 303