Fixes #4917. Kitty Keyboard Protocol doesn't works with AltGr and with empty fields

[BDisp]

Fixes

• Fixes Kitty Keyboard Protocol doesn't works with AltGr and with empty fields #4917
• Fixes Invalid global.json file with "sdk" version #4867

Proposed Changes/Todos

• ModifierKey.AltGr
• Add keypad keys

Pull Request checklist:

• I've named my PR in the form of "Fixes #issue. Terse description."
• My code follows the style guidelines of Terminal.Gui - if you use Visual Studio, hit CTRL-K-D to automatically reformat your files before committing.
• My code follows the Terminal.Gui library design guidelines
• I ran dotnet test before commit
• I have made corresponding changes to the API documentation (using /// style comments)
• My changes generate no new warnings
• I have checked my code and corrected any poor grammar or misspellings
• I conducted basic QA to assure all features are working

[tig]

I pushed some changes to simplifiy enablement.

I'm confused about whether this is a WIndows only issue or not.

Do you know that it doesn't exist on other platforms?

[BDisp]

Your commit c969d3f broke keyboard kitty support. Please review it. Thanks.

[tig]

@BDisp please remove the fix for #4918 from this PR. Your fix is not at the right level and adds unnecessary coupling of kitty specific details into the IInput/AnsiInput code.

Your fixes for the other two issues are fine though.

The correct solution to #4918 needs to go in InputProcessorImpl and AnsiInputProcessor; in ProcessAfterParsing we need to give derived processors a chance to suppress keydown events that come from fallback stream processing after ANSI parsing.

I have a robust set of tests and fix in #4927.

[BDisp]

I already remove all the changes related with the #4918. I hope I didn't breaking anything. Thanks.