Jetpack status CLI displays incorrect blog ID in multisite when connecting

#### Steps to reproduce the issue

1. Run a command that includes a call to `jetpack status`, (e.g. `jetpack start-connect --network` in VIP env) in multisite
https://github.com/Automattic/vip-go-mu-plugins/blob/master/jetpack-start/wp-cli-provision.php

2. The output will show that each site is being connected to the same cache site blog ID.

3. But in reality they are different (you can check this by running `wp jetpack status` sometime later, the blog IDs are different.

#### What I expected
show different blog ids from this call across the multisite, since each subsite has its own blog id - https://github.com/Automattic/jetpack/blob/master/class.jetpack-cli.php#L67

#### What happened instead
Same blog id shows - but I am not sure why. Perhaps it is an issue with alloptions cache?

#### Output
Sample output: 21897-pb
report: p73hgi-1Om-p2

Start with class.jetpack-cli.php around line 67 and reproduce the reported command, such as `jetpack start-connect --network` or `wp jetpack status`, in a multisite environment. Compare the displayed blog IDs for each subsite with the later `wp jetpack status` output. Done means the connection status reports each subsite's actual, distinct blog ID.

Written by the indexing model from the issue text.