[security] split multi-node operators into different asgards

Fixes #1597 (closed) Related #1617

added churn-or-bond label

assigned to @son-of-odin

My own inclination for this would be to just go ahead and implement some sort of random shuffle that has been discussed previously, since it's a super set and also prevents collusion.

changed milestone to %Release-1.118.0

added 14 commits

• 78173db4...07f4b653 - 13 commits from branch develop
• 00c07100 - split multi-node operators into different asgards

Compare with previous version

added 2 commits

• d139df9b - no logic changes
• f5c17246 - split multi-node operators into different asgards

Compare with previous version

changed the description

added 2 commits

• 5363d8f3 - no logic changes
• 9aa43cda - split multi-node operators into different asgards

Compare with previous version

approved this merge request

resolved all threads

added 6 commits

• 9aa43cda...aa646f1b - 3 commits from branch develop
• 1e85ca8e - no logic changes
• 92774ded - split multi-node operators into different asgards
• 2ba62c5e - ursa feedback

Compare with previous version

changed milestone to %Release-1.119.0

added 7 commits

• 2ba62c5e...30115cba - 3 commits from branch develop
• 1e4fcc42 - no logic changes
• 310f9316 - split multi-node operators into different asgards
• 8e31e832 - ursa feedback
• c2a5c964 - bump version

Compare with previous version

approved this merge request

added 5 commits

• c2a5c964...707e5d01 - 3 commits from branch develop
• 998d699e - split multi-node operators into different asgards
• 21241c2f - ursa feedback

Compare with previous version

approved this merge request

approved this merge request

merged

changed the description