feat: move the algod client to store

[acfunk]

This is to address issue #213

• replaced the algodClient prop on the WalletManager with a getter and setter that point to the store
• removed algodClient from persisted storage - the re-serialization makes it useless anyway
• setActiveNetwork on store now takes algodClient as a parameter
• tests were updated to reflect the changes

[drichar]

Appreciate you splitting this from your other PR so the changes can be addressed separately. Overall this looks good, and most of my change requests are minor optimizations. The important one is making sure loadPersistedState has the correct return type.

While this does handle moving the algod client to the store in the core library, I'm curious whether this now works as expected in your Vue app (AlgoTools)? When @SilentRhetoric made his PR to fix network switching in the Solid adapter, the critical change was moving the algod client to the @tanstack/solid-store reactive store.

The way he described it to me, I would have expected something similar to get it working properly in the Vue adapter: accessing the algodClient like this:

const algodClient = useStore(manager.store, (state) => state.algodClient)

and having that be what's returned from its useWallet composable function.

That's what I was planning to do in the Vue and React adapters when I created #213. Your changes here were also needed! I was just expecting the framework-specific reactive stores to also be part of the solution.

[acfunk]

That's what I was planning to do in the Vue and React adapters when I created #213. Your changes here were also needed! I was just expecting the framework-specific reactive stores to also be part of the solution.

Vue reactivity is handled in WalletManagerPlugin with const algodClient = ref(manager.algodClient).
I'll take a look at React.

EDIT: The React WalletProvider also already handles reactivity of algodClient.

[drichar]

Looks great! LGTM