Use TextDocumentChangeRegistrationOptions for didChange registration

[ryzngard]

When dynamically registering for razor, the didChange was registered incorrectly. This changes to make sure the change exist and uses incremental, which is what xaml registers as

Confirmed didchange LSP event in the LSP logs

[Trace - 6:13:47 PM] Sending notification 'textDocument/didChange'.
Params: {
    "textDocument": {
        "uri": "file:///s:/BlazorServer/Pages/Counter.razor",
        "version": 2
    },
    "contentChanges": [
        {
            "range": {
                "start": {
                    "line": 16,
                    "character": 24
                },
                "end": {
                    "line": 16,
                    "character": 25
                }
            },
            "rangeLength": 1,
            "text": ""
        }
    ]
}

[ryzngard]

Thanks @dibarbet for helping me track down this issue :)

[ryzngard]

The sync kind was more important here, but I went ahead and updated the documentFilter as well