Implementing COMMAND DOCS

[TalZaccai]

• Added support for COMMAND DOCS command
  • All supported command docs are located in Garnet.server/Resp/RespCommandsDocs.json
• Added support for specifying docs path in command registration using the REGISTERCS command
• Added support for specifying command docs when registering command programatically
• Updated CommandInfoUpdater tool to import existing RESP command docs and unify them with Garnet-specific command docs
  • All Garnet-specific command docs are located in CommandInfoUpdater/GarnetCommandsDocs.json
• Updated RespCommandInfo to use "flattened-style" RespCommand enum for sub-commands
• Fixed COMMAND INFO to return sub-command info when called with sub-command name
• Added COMMAND DOCS tests & updated website docs

Examples:

• Autocompletion of Garnet-specific commands:
  
• Autocompletion of custom commands (requires restarting the client for it to refresh the docs):
  

[badrishc]

Please check the binary size compared to main, and if it looks reasonable, we can merge.

[TalZaccai]

Please check the binary size compared to main, and if it looks reasonable, we can merge.

I've moved the json files to a separate dll that is being loaded (and unloaded) dynamically. The size of Garnet.server.dll is now down to 635KB. Let me know if you like the current solution. The loading & unloading of the assembly would happen at most twice (once for command info init & once for command docs init, on an as-needed basis) and is synchronized as to not cause any issues (Look at RespCommandDataCommon.cs for implementation)

Note: I packed and tested the nuget package locally and it works.

[badrishc]

Please check the binary size compared to main, and if it looks reasonable, we can merge.

I've moved the json files to a separate dll that is being loaded (and unloaded) dynamically. The size of Garnet.server.dll is now down to 635KB. Let me know if you like the current solution. The loading & unloading of the assembly would happen at most twice (once for command info init & once for command docs init, on an as-needed basis) and is synchronized as to not cause any issues (Look at RespCommandDataCommon.cs for implementation)

Note: I packed and tested the nuget package locally and it works.

LGTM