[CI] use sklearnex azure pipelines template for sklearnex CI step

[icfaust]

Description

oneDAL should refer to sklearnex's testing rather than storing scripts on its own locally. This is a maintenance burden that we can remove. No performance benchmarks are necessary. This PR has been enabled by uxlfoundation/scikit-learn-intelex#2125 in order to use the PR-generated GNUMKL build.

---

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]

/intelci: run

[icfaust]

/intelci: run

[Alexandr-Solovev]

should it be called here? May be its better to call both functions? And why we must include it in MKL?

[icfaust]

Good question @Alexandr-Solovev, why tbb install was included in mkl I do not know (included in the 2025.0 update I think), but I called one function in the other so that we only have to change the tbb version in one location going forward. Let me know if I should change it.

[Alexandr-Solovev]

current changes look good for me