Fix eager compilation with signature for dppy.kernel

[reazulhoque]

Closes #75

This will fix the seg-fault issue when signature was provided with dppy.kernel.

Eager compilation is still Just-In-Time compilation. Instead of the compilation happening at the call site it happens at the definition site. We have caching mechanism for already compiled kernels that takes the SYCL queue in account. This
mechanism can be potentially used to recompile a kernel that has been compiled for a different backend (Sycl queue).

Steps taken to fix this:

• Make sure when we provide signature, that triggers the eager compilation, we go through the existing caching mechanism. If the Sycl queue is consistent we simply launch the kernel in other cases we recompile for the given queue.

[PokhodenkoSA]

Please fix CI on Windows.

[PokhodenkoSA]

Can we test AOT somehow?

[PokhodenkoSA]

@reazulhoque please merge with main. It will fix black.

[PokhodenkoSA]

I am continuing to review.

[PokhodenkoSA]

Much better. I have made remarks with useful links describing how to make better.

[PokhodenkoSA]

https://stackoverflow.com/questions/1325581/how-do-i-check-if-im-running-on-windows-in-python
it shows that it is better to rely on os.name == 'nt'.

[reazulhoque]

The question directs to an already answered question which suggests sys.platform.

[PokhodenkoSA]

platform.system() == "Windows"

[PokhodenkoSA]

This PR does not fix #75. Because the test uses func.specialize(..., gpu_queue) and the issue have another scenario.
@reazulhoque you should provide test like in issue to prove that the issues is fixed.

[reazulhoque]

@PokhodenkoSA, this PR solves #75. There are multiple tests that needed to be updated, which test are you talking about when you mention func.specialize(..., gpu_queue)?

I have updated tests with signatures that will trigger eager compilation. I asked Numba team specifically if they have tests for eager compilation and they mentioned they do not. I decided to not write specific tests following that conversation.

When I add signature to @dppy.kernel in exisiting test it follows the example I have provided in #75. Tests I have updated to make sure eager compilation is working:

1. https://github.com/IntelPython/numba-dppy/pull/291/files#diff-b7c075c42e2cbadf69e707181714af75c0c8a705a806e2e2f71345253fc7af73R56
2. https://github.com/IntelPython/numba-dppy/pull/291/files#diff-b7c075c42e2cbadf69e707181714af75c0c8a705a806e2e2f71345253fc7af73R81
3. https://github.com/IntelPython/numba-dppy/pull/291/files#diff-b7c075c42e2cbadf69e707181714af75c0c8a705a806e2e2f71345253fc7af73R108

[PokhodenkoSA]

I agree with test changes. Need CI fix and use platform.system().