[SYCL] Move Kernel specific data from handler_impl to a separate data structure

[vinser52]

This PR is a prerequisite for the handler-less API.
Kernel-specific data and argument parsing logic are moved from the handler_impl to the new KernelData class that will be used in a handler-less path.

[vinser52]

There are two functional changes in this PR (this line and line 241). Before these changes, the handler::registerDynamicParameter method was used to add a dynamic parameter. The handler::registerDynamicParameter method has two checks that might throw exceptions. Since the processArg function is moved from handler to the KernelData we cannot use handler::registerDynamicParameter. I also cannot move the registerDynamicParameter to the KernelData class because it requires to access Queue and Graph from the handler.

[aelovikov-intel]

I was thinking about something like this: https://godbolt.org/z/jjG5zsb5z

@vinser52 , @sergey-semenov , WDYT?

The link above introduces

struct KernelData { /* information about device kernel */ };
struct SubmissionInfo { /* information about what's being submitted, including KernelData */ };

I think there will be a need for at least one other data structure to pass from handler to scheduler that will be encapsulating SubmissionInfo along with some other information filled in handler/no-handler submission path before reaching either scheduler or direct UR enqueue APIs.

[aelovikov-intel]

This mixes data specific to the kernel (i.e., as generated by the device compiler) and the current submission of that kernel. I believe those pieces should belong to different data structures. @Alexandr-Konovalov has introduced some SubmissionInfo few weeks/months ago. I think MKernelFuncPtr belongs there and not with things like MKernelNumArgs and MKernelIsESIMD.