fix: make algorand client persistent for test fixture

[joe-p]

Proposed Changes

• Restores algorand client to be persistent for a given fixture as it was in ad7dc8e

[joe-p]

This is seemingly breaking tests inconsistently but not entirely sure why. I can investigate further but if anyone has some insight that would be appreciated. @robdmoore do you know why this was changed in the first place?

[neilcampbell]

@joe-p Yeah that's why it was changed.
From memory it was due to parallel test execution resulting in a non thread safe like behaviour (obviously no threads in JS) on the AlgorandClient.

Because AlgorandClient is stateful, it's possible for a test to change the AlgorandClient internal state, whilst another test is also being executing. I'm assuming it's whilst an async function is being awaited or something like that.