Fix CompletionItem.data type

The LSP 3.17 spec declares it as an optional LSP_Any field.

This caused issues with GNAT Studio when trytong to parse GLS completion
responses.

For eng/ide/gnatstudio#141

Author: AnthonyLeonardoGracio

source/gpr/lsp-gpr_completions.adb

@@ -268,7 +268,8 @@ package body LSP.GPR_Completions is
    end Fill_Completion_Response;
 
    procedure Fill_Completion_Resolve_Response
-     (Response : in out LSP.Structures.CompletionItem) is
+     (Response : in out LSP.Structures.CompletionItem)
+   is
       Pack     : Package_Id;
       Attr     : Q_Optional_Attribute_Id;
       Doc_Text : VSS.Strings.Virtual_String;

source/protocol/generated/lsp-message_io.adb

@@ -7080,7 +7080,7 @@ package body LSP.Message_IO is
             elsif Key = "command" then
                Optional_Command'Read (S, V.command);
             elsif Key = "data" then
-               Optional_Location'Read (S, V.data);
+               Optional_LSP_Any'Read (S, V.data);
             else
                JS.Skip_Value;
             end if;
@@ -7130,7 +7130,7 @@ package body LSP.Message_IO is
       JS.Key ("command");
       Optional_Command'Write (S, V.command);
       JS.Key ("data");
-      Optional_Location'Write (S, V.data);
+      Optional_LSP_Any'Write (S, V.data);
       JS.End_Object;
    end Write_CompletionItem;
 

source/protocol/lsp-messages.ads

@@ -7625,7 +7625,7 @@ package LSP.Messages is
       additionalTextEdits : TextEdit_Vector;
       commitCharacters    : Optional_Virtual_String_Vector;
       command             : Optional_Command;
-      data                : Optional_Location;
+      data                : Optional_LSP_Any;
    end record;
 
    procedure Read_CompletionItem