Cannot Unstake chains that have fallen out of sync/crashed/need a resync/update of chain changes API methods or calls/etc

[alexpeterson91]

Describe the bug
Currently we cannot unstake chains that have fallen out of sync/crashed/need a resync/update of chain changes API methods or calls/etc, because the node will respond to its state check with a 1 for syncing or a 0 for not installed, making the checkbox grayed out and non clickable. Users rack up losses mess up the quality of the network because they now have an unsynced chain that is staked and thus cannot be unselected and cannot be restaked.

To Reproduce
DONT DO THIS ON MAINNET
Install Pokt sync pokt stake a node sync and stake any other non Pokt chain i.e. NEAR. now to simulate the condition of when something falls out of sync, delete the NEAR volume, now you'll see that your NEAR node in the Pokt UI that was checkable and said running, is now grayed out but still checked listed as syncing. you cannot deselect it because it's state is returning a syncing state not synced. Only way around this right now is to SSH into your node, attach a terminal to the pocket container and run the stake command without the unsynced chain.

Expected behavior
What should happen is that when a chain is staked and it then falls back to syncing or not installed for whatever reason the check box should not be disabled for chains that are already staked

Screenshots

In this shot i have both NEAR and Arbitrum One in this situation, had an internet outage and these took a very long time to come back in sync. Only way i could unstake them was manually via CLI over SSH.

[alexpeterson91]

I have yet to come up with an elegant way to implement a fix in the UI since it would need to add an entire new state store and then check of previously synced chains, while this doesnt need a new store per se, since it can just do an RPC call to its own pokt node requesting chains staked and then adding a 4th state to the chain readiness check, accounting for staked relay chains, and if its currently not "running" and is "syncing" and or "not installed" that it also enables the button so that it can be unstaked despite not being synced.

My workaround is to simply inspect the page, specifically the relevant button then edit the button attributes from disabled to enabled, and then uncheck it, do the same for any others that are in the same place, then restake, fixes it fine everytime, but its not user fiendly, Must add nested if statement to account for this confition, just as i did with pruned pokt chains that are synced but cannot be staked.