`rangeFormatting` is used to register whole-document `formatting` capability

Describe the bug

The language server seems to be checking the wrong capability (rangeFormatting) to determine whether to dynamically register its whole-document formatting capability with the client.

There's an easy workaround (set a rangeFormatting capability on the client) but it's not immediately apparent without reading through the code.

clientDynamicRegisterSupport is set here based on the client's rangeFormatting capability:
https://github.com/redhat-developer/yaml-language-server/blob/6eda5f6168bb326883f5fd44508788c089d78b22/src/yamlServerInit.ts#L79-L83

But it's later used to dynamically register the whole-document formatting capability here:
https://github.com/redhat-developer/yaml-language-server/blob/0080b8c63d24e64be6dd1f759cfdb9a0d86c6d90/src/languageserver/handlers/settingsHandlers.ts#L162-L164

Thanks for all your work on this great project! 🙂

Expected Behavior

The language server should look at the client's formatting capability to determine whether to dynamically register its formatting capability

Current Behavior

The language server currently looks at the client's rangeFormatting capability to determine whether to dynamically register its formatting capability

Steps to Reproduce

1. Create a client that registers the formatting (not rangeFormatting) capability and observe that it never receives a client/registerCapability request from the server
2. Change the client to register the rangeFormatting capability and observe that the sever then sends a client/registerCapability request for formatting

Environment

• Windows
• Mac
• Linux
• other (please specify)

Start in src/yamlServerInit.ts at the clientDynamicRegisterSupport assignment, then compare its use in src/languageserver/handlers/settingsHandlers.ts. Confirm that the client's formatting capability controls dynamic registration, and verify the reproduction steps with formatting enabled but rangeFormatting disabled.