[SYCL][ESIMD][E2E] Fix ambiguity in device descriptor usages in ESIMD tests

[againull]

Follow-up after #15905
These tests use using directive for both sycl and esimd namespaces and info is available in both, so we have to explicitly specify namespace in this case to avoid ambiguity.

Hasn't been noticed before because tests run only on pvc.

[sarnex]

lgtm but do we know why it started failing now? did we add an include somewhere in the last PR or something?

also can you please add [ESIMD] after [SYCL] in the PR title?

[againull]

lgtm but do we know why it started failing now? did we add an include somewhere in the last PR or something?

also can you please add [ESIMD] after [SYCL] in the PR title?

These tests didn't fail initially because they have "requires: pvc" and we don't build/run such tests in intel/llvm CI.

[sarnex]

right, but i run testing manually on pvc somewhat often and i don't remember seeing this many failures. do we know why the previous PR was related?

[againull]

right, but i run testing manually on pvc somewhat often and i don't remember seeing this many failures. do we know why the previous PR was related?

Before previous PR we had sycl::info and sycl::ext::intel::info namespaces. Previous PR also introduced info into sycl::ext::intel::esimd namespace. So, if both sycl and sycl::ext::intel::esimd are included by means of using directive then there is a name collision and we have to explicitly specify which info we want to use.

[sarnex]

ok thanks that exactly answers my question!