fix: update docker container running alert

[zachfedor]

Match an update to the Stellar-CLI from this PR that broke how we determined if a container was already running. Currently, scaffold build will error out if the container is already running because the string mismatch, or logic assumes there was an error with it instead of continuing on with the health check.

[willemneal]

@copilot Can you fix the clippy errors

[Copilot]

@willemneal I've opened a new pull request, #393, to work on those changes. Once the pull request is ready, I'll request review from you.

[zachfedor]

@willemneal, it took me a while to hunt this down, but I think I found a problem from your PR that updated scaffold to use stellar-cli v25, specifically these lines. I think the deploy_contract function was using the wrong network configuration, and since that didn't include --rpc-url or --network-passphrase, the parsed config had no network info which was causing get_remote_wasm_from_hash to fail with "Contract Code not found" on my system when trying to build clients.

No need to look now, I can explain better tomorrow in our weekly update.