Fix client localSchemaFile for vscode stats command

[JakeDawkins]

Currently, if you click on the Apollo logo on the status bar, stats for the project you're working with are supposed to show, to confirm the config was setup properly and the extension has loaded.

If you're setting up a client project and using a localSchemaFile though, the stats will fail to load unless there is a service name also provided, which isn't required.

This removes the check in the stats loading function that forced a client to have a client.service.name even if not using graph manager to load the schema.

TODO:

• Update CHANGELOG.md* with your change (include reference to issue & this PR)
• Make sure all of the significant new logic is covered by tests
• Rebase your changes on master so that they can be merged easily
• Make sure all tests and linter rules pass

*Make sure changelog entries note which project(s) has been affected. See older entries for examples on what this looks like.

[trevor-scheer]

Can we tell if there's another configuration path where serviceID is required that this might affect? We might want something more like:

Boolean((this.serviceID || this.localSchemaFile) && (this.schema || this.serviceSchema))

This is just a stab / guess.

[JakeDawkins]

@trevor-scheer I can check, but since this is only used for logging output to vscode, I don't think that'd matter. I tried something similar to what you dropped in but TS was v. angry 🙃