[fix] changes for GitHub actions PR CI for matching oneDAL Nightly-build

[icfaust]

Description

Fixes to return CI to green as Nightly-build was changed in uxlfoundation/oneDAL#2865 and uxlfoundation/oneDAL#2920

No operational changes made, thus benchmarking unnecessary.

---

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.

Performance

• I have measured performance for affected algorithms using scikit-learn_bench and provided at least summary table with measured data, if performance change is expected.
• I have provided justification why performance has changed or why changes are not expected.
• I have provided justification why quality metrics have changed or why changes are not expected.
• I have extended benchmarking suite and provided corresponding scikit-learn_bench PR if new measurable functionality was introduced in this PR.

[icfaust]

Still a problem with kneighbors and stability, this probably will need to be deselected and a ticket made for investigation.

[icfaust]

Still to be done: ticket for investigations on kneighbors stability issues. Ideally the CI should be re-run 8-10x to make sure I caught all the intermittent failures. I need to add the additional sparsity deselections to the sparsity investigation ticket, and is exhibited both in Intel and non-Intel hardware.

[icfaust]

/intelci: run

[icfaust]

/intelci: run

[icfaust]

/intelci: run

[samir-nasibli]

I propose to make a common function for checking and disabling as the nature of these crashes is the same.
Also less code duplication

def _skip_neighbors(estimator, method):
    if (
        not _IS_INTEL
        and ("Neighbors" in estimator or "LocalOutlierFactor" in estimator)
        and method in ["score", "predict", "kneighbors", "kneighbors_graph"]
    ):
        if daal_check_version((2025, "P", 200)):
            pytest.fail("Re-verify failure of algorithms in 2025.2 oneDAL")
        pytest.skip(f"{estimator} shows instability on Non-Intel hardware")

Suggested change

	if (
	not _IS_INTEL
	and ("Neighbors" in estimator or "LocalOutlierFactor" in estimator)
	and method in ["score", "predict", "kneighbors", "kneighbors_graph"]
	):
	if daal_check_version((2025, "P", 200)):
	pytest.fail("Re-verify failure of algorithms in 2025.2 oneDAL")
	pytest.skip(f"{estimator} shows instability on Non-Intel hardware")
	_skip_neighbors(estimator, method)

[samir-nasibli]

@icfaust thank you for the work done! Seems we have green ci now.
#2081 is already merged. Please rebase and address comments. Good to go!

[samir-nasibli]

don't have permissions to Ian's branch. Going to merge this and add refactoring my suggestion as a follow up. Don't want to block green CI enabling