[fix] ensure consistent hook sorting by name

[fuldaxxx]

Overview

Improve hook sorting by adding a secondary sort criterion based on hook names when orders are equal. This ensures consistent ordering of hooks with the same order value.

What this PR does / why we need it

Hooks with the same Order value were executed in a non-deterministic order. This matters because an earlier hook can perform a check and set a value, allowing subsequent hooks to skip the check and simply read that value — but this pattern breaks when execution order is unpredictable.
The fix adds a secondary sort by hook name when Order values are equal, so hooks with the same priority are now always executed in alphabetical order.

Before:

~ kubectl logs -n d8-system deploy/deckhouse | grep 'kubernetesSynchronization' |   grep '"module":"r-g-test"' | jq -r '.hook'

hooks/batchhooks:batch/c-test:2
hooks/batchhooks:batch/e-test:4
hooks/batchhooks:batch/f-test:5
hooks/batchhooks:batch/g-test:6
hooks/batchhooks:batch/h-test:7
hooks/batchhooks:batch/a-test:0
hooks/batchhooks:batch/d-test:3
hooks/batchhooks:batch/b-test:1

After:

~ kubectl logs -n d8-system deploy/deckhouse | grep 'kubernetesSynchronization' |   grep '"module":"r-g-test"' | jq -r '.hook'

hooks/batchhooks:batch/a-test:0
hooks/batchhooks:batch/b-test:1
hooks/batchhooks:batch/c-test:2
hooks/batchhooks:batch/d-test:3
hooks/batchhooks:batch/e-test:4
hooks/batchhooks:batch/f-test:5
hooks/batchhooks:batch/g-test:6
hooks/batchhooks:batch/h-test:7