Fix fetching nested http settings

[robb-j]

What does this PR do?

This PR tweaks the way the http configuration section is pulled from the client. It pulls the entire http section at once then plucks out the values it needs. I do assume there is no sensitive client information other that proxy and proxyStrictSSL on the http section which shouldn't be pulled.

In my research I've found no solid definition for what a section in the LSP is so my thinking is that usage of it should be as simple as possible for most clients to support it.

What issues does this PR fix or reference?

Nova doesn't currently have a way to configure how workspace settings are passed to the server and it does it in a bit of an odd way at the moment, which I've described in the issue below. Requesting http.proxy in Nova returns {} which was getting passed straight to requests_light and breaking it.

• Upgrade server to 0.20 robb-j/nova-yaml#20

Is it tested? How?

With unit tests. I updated the existing unit test to follow the new LSP message structure and added an assertion for the shape of settings passed to setConfiguration.

I ran the modified server in Nova using npm link and confirmed that schemas were being loaded and tooltips were showing again.

I can try running it with VSCode if you like but I don't currently have an extension development setup for it.

[evidolob]

@robb-j Could you fix build?

[coveralls]

Coverage decreased (-0.01%) to 78.144% when pulling 82de081 on robb-j:main into e44fc1b on redhat-developer:main.

[robb-j]

That's fixed, it was a code formatting issue in the test.