fix(ci): correct crate publish tier ordering in release workflow

nodedb-crdt and nodedb-fts depend on nodedb-types and belong in TIER3,
not TIER1. nodedb-types depends only on nodedb-codec (a TIER1 crate)
and belongs in TIER2, not after crates that depend on it.

Author: farhan-syah

.github/workflows/release.yml

@@ -120,14 +120,14 @@ jobs:
           CARGO_REGISTRY_TOKEN: ${{ secrets.CARGO_REGISTRY_TOKEN }}
         run: |
           # Tier 1: no internal NodeDB dependencies
-          TIER1="nodedb-codec nodedb-bridge nodedb-wal nodedb-mem nodedb-crdt nodedb-raft nodedb-fts"
-          # Tier 2: depends on tier 1 only
+          TIER1="nodedb-codec nodedb-bridge nodedb-wal nodedb-mem nodedb-raft"
+          # Tier 2: depends on tier 1 only (nodedb-types depends on nodedb-codec)
           TIER2="nodedb-types"
-          # Tier 3: depends on tier 1-2
-          TIER3="nodedb-vector nodedb-graph nodedb-spatial nodedb-strict nodedb-client nodedb-columnar nodedb-cluster"
-          # Tier 4: depends on tier 3 (nodedb-spatial, nodedb-fts, nodedb-types)
+          # Tier 3: depends on tier 1-2 (all depend on nodedb-types)
+          TIER3="nodedb-fts nodedb-crdt nodedb-vector nodedb-graph nodedb-spatial nodedb-strict nodedb-client nodedb-columnar nodedb-cluster"
+          # Tier 4: depends on tier 3 (nodedb-query depends on nodedb-spatial, nodedb-fts)
           TIER4="nodedb-query"
-          # Tier 5: depends on tier 4 (nodedb-query)
+          # Tier 5: depends on tier 4 (nodedb-sql depends on nodedb-query)
           TIER5="nodedb-sql"
           is_published() {
             curl -sf \