Passive and Active node never exposed with specific sentry nodes support

[branciard]

implement #216

6 nodes federation never expose Passive and Active nodes (1,2,3).
Sentry nodes 4,5,6 are specifically define.

3 federation nodes as before is always possible.
The previous zip config format is also supported.

3 nodes federation roles (as before)
All 3 nodes are operator.

Node	Role
archipel-node-1-{active or passive-sentry}	operator
archipel-node-2-{active or passive-sentry}	operator
archipel-node-3-{active or passive-sentry}	operator

6 nodes federation roles

3 nodes (1,2,3) are operator. 3 nodes ( 4,5,6) are sentry.

Node	Role
archipel-node-1-{active or passive}	operator
archipel-node-2-{active or passive}	operator
archipel-node-3-{active or passive}	operator
archipel-node-4	sentry
archipel-node-5	sentry
archipel-node-6	sentry

Migration workflow :
Migration from 3 nodes federation to 6 nodes federation have been tested also. to be able to upgrade current setup without downtime (or few seconds as an polkadot version update ). Here the test :

1. Install only 3 new sentry nodes of a 6 federation config. 3 previous federation nodes ( active/passive) are not impacted and can be updated to the latest version of archipel. ( old config zip format is supported)

2. copy polkadot peers ID id from old zip 3 federation nodes 1,2,3 and add them in the new zip config of the 6 nodes federation. ( to do not change polkadot peers ID suppervise by web3 foundation )
3. Force 3 old operator 1, 2, 3 to be passive with env var : (start with 2 passive ones, to have less validator downtime)
   ARCHIPEL_SUSPEND_SERVICE=true
4. Remove volume archipel on 3 operators to synch archipel chain on the new federation on 6 nodes
5. Reactivate orchestration with ARCHIPEL_SUSPEND_SERVICE=false
6. Enjoy your new secure 6 nodes federation :