bug: Pulling a currently stopped instance and then deploying that instance causes an error

[Chriztiaan]

This is a potential edge case that has unexpected behaviour:

Pull 
Link
Stop
Deploy
....
Works as expected

Clear powersync config directory.

Skip Pull
Link
Stop << works
Deploy << fails because no powersync service config
Pull
Deploy << fails with:
Performing validations before deploy...
        Validating configuration...
        Testing connections...
        Validating sync config...
Error: Failed to validate sync config for instance 68f750e983e57bcac0056d91 in project 68dd39acc5212f000714e7a9 in org 68dd38e11b90d300074d597c. Ensure the sync config is valid before

Notes from Steven:

The stop command doesn't require config to be locally available. So it makes sense that it works. Then the deploy command does need config in order to deploy. Makes sense. The deploy after the pull should have detected the instance has been deprovisioned and then reprovision it.