Ticking without ARB packet / Improvement on computor list

[philippwerner]

Currently list of future computors is just copied as is. We need the following improvement: If a computor has kept its status then it must keep its computor index.
nodes can generate the new comp list themself and continue ticking thru new epoch. (no downtime)

Related: https://discord.com/channels/768887649540243497/1087017597133922474/1208492862895824936

Current Behavior: After transitioning to a new epoch, all network nodes must wait for an ARB packet to resume operation.

Improvement: Nodes that successfully perform an automatic epoch switch possess sufficient data to determine the new computor list. They can continue ticking without waiting for the ARB packet.
ARB can broadcast the packet later for verification.

Expected Outcome: Reduced network latency during epoch transitions.

[fnordspace]

Depends on qubic/qubic-cli#55 so that solutions get accepted.

[fnordspace]

After conversation with CfB requirements changed:

• If ARB list does not match the selfComputedComputor list node shall stop ticking without the option to continue, even if a corrected list of Arb arrives.
• SelfComputedComputorList shall be saved in system file