guardian-ui: fix config verification

[okjodom]

At the config verification step after all the guardians have verified other configs, if the leader continued their own setup to completion before the follower guardians, there is a chance the followers would not be able to resume and complete their setup since we relied on their servers being able to continuously poll the leader's server for consensus configuration.

This PR fixes the bug, allowing all guardians to complete federation set-up in any order, provided they have successfully coordinated through config verification.

Steps to validate

1. Before fix:

• Follow federation set-up through config verification until you see "All guardians have verified their codes"
• Reload any guardians setup page to confirm that the verified codes are automatically pre-filled on reload
• Complete set-up for the leader
• Reload the page for any other guardian and observe that config verification shows an error. The verification page expects the leader's server to still be in set up and not in consensus running

2. After fix:

• Follow federation set-up through config verification until you see "All guardians have verified their codes"
• Reload any guardians setup page to observe that the verified codes are automatically pre-filled on reload
• Complete set-up for the leader
• Reload the page for any other guardian and observe that the verified codes are automatically pre-filled on reload
• Confirm you can complete set-up for these "follower" guardians

Fixes #255

[wbobeirne]

@okjodom I hit continue with the leader before verifying all configs on all followers, and got stuck on this screen:

Is this a regression from fedimint/fedimint#3547? I was unable to get this to happen in master.

[okjodom]

@okjodom I hit continue with the leader before verifying all configs on all followers, and got stuck on this screen:

Is this a regression from fedimint/fedimint#3547? I was unable to get this to happen in master.

do you mean current repo master, or upstream master? trying a repro

[wbobeirne]

Apologies, I meant fedimint/ui@master using the version of devimint pegged in the flake.nix, which was 23ee7cb6e96fce89bb024fbc1fcfccbfb3dc968b at the time of my run.

[okjodom]

Apologies, I meant fedimint/ui@master using the version of devimint pegged in the flake.nix, which was 23ee7cb6e96fce89bb024fbc1fcfccbfb3dc968b at the time of my run.

Figured I didn't properly update flake lock - now it's taking forever to recompile devimint after bump🤦🏿‍♂️

[okjodom]

help me close this bug, @wbobeirne , @Kodylow

[Kodylow]

Ran the tests with this yesterday closing leader's tab and refreshing everything, looks good to me.

[okjodom]

thanks for the review. landing fix