[Fix] [Array API] Raise AttributeError for non-homogen tables in __sycl_usm_array_interface__ to comply with Python interop expectations

[KateBlueSky]

Raise AttributeError for non-homogen tables in sycl_usm_array_interface to comply with Python interop expectations

This PR updates the behavior of the sycl_usm_array_interface property for oneDAL table objects to improve compatibility with Python SYCL-aware libraries (e.g. dpctl, dpnp, numba-dpex).

Previously, the property handler used report_problem_to_sua_iface(": only homogen tables are supported");
to signal unsupported table types (e.g., sparse or non-homogen tables). However, this results in a non attribute related error being raised, which breaks compatibility with Python’s hasattr() behavior, and can surface as runtime errors in downstream libraries that probe for SYCL USM compatibility.

The fix aligns with Python data protocol conventions (e.g., array_interface, cuda_array_interface), which require AttributeError to signal absence.

Checklist to comply with before moving PR from draft:

PR completeness and readability

• I have reviewed my changes thoroughly before submitting this pull request.
• I have commented my code, particularly in hard-to-understand areas.
• I have updated the documentation to reflect the changes or created a separate PR with update and provided its number in the description, if necessary.
• Git commit message contains an appropriate signed-off-by string (see CONTRIBUTING.md for details).
• I have added a respective label(s) to PR if I have a permission for that.
• I have resolved any merge conflicts that might occur with the base branch.

Testing

• I have run it locally and tested the changes extensively.
• All CI jobs are green or I have provided justification why they aren't.
• I have extended testing suite if new functionality was introduced in this PR.

[icfaust]

@KateBlueSky Good catch! Does this mean that csr_tables would fail hasattr calls previously?

[KateBlueSky]

@KateBlueSky Good catch! Does this mean that csr_tables would fail hasattr calls previously?

yes, it would throw a runtime error in the original code.

[icfaust]

/intelci: run

[codecov]

Codecov Report

❌ Patch coverage is 0% with 1 line in your changes missing coverage. Please review.

Files with missing lines	Patch %	Lines
onedal/datatypes/sycl_usm/data_conversion.cpp	0.00%	1 Missing ⚠️

Flag	Coverage Δ
azure	80.81% <ø> (?)
github	73.24% <0.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
onedal/datatypes/sycl_usm/data_conversion.cpp	33.33% <0.00%> (ø)

... and 29 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[KateBlueSky]

/intelci: run

[KateBlueSky]

/intelci: run