engine: bump orchestra.json version number

[bassosimone]

This issue is part of the work required to replace orchestra with api.ooni.io, as discussed with @FedericoCeratto. The general idea here is to consider the current orchestra.json state on disk as having an implicit Version set to 0 and consider that file obsolete. The code will register again and login again, adding (1) the hostname with which it is registering to the data format, so we can switch between prod and testing API seamlessly and (2) add Version set to 1. This change needs to happen after we have migrated the orchestra API endpoints to use api.ooni.io and ooni/api as opposed to ooni/orchestra.