MAINT: align daal4py, onedal and sklearnex modules with isort and black

[samir-nasibli]

Description

Advantage:

• Aligned with isort and black whole proj.
• This helps avoid messing up new PRs with refactoring and makes review easier.

Commit message will be "apply isort and black fixes only for daal4py, onedal and sklearnex modules"

Disadvantage:

• this messing up files blame

[ahuber21]

Actually normalizing the entire project is something that I wanted to avoid. I think the commit history in rarely changed files (e.g. the code generators) is more important than code formatting.
Also, why --skip-string-normalization ?

[samir-nasibli]

Actually normalizing the entire project is something that I wanted to avoid. I think the commit history in rarely changed files (e.g. the code generators) is more important than code formatting. Also, why --skip-string-normalization ?

As I mentioned on the description, it seems to me that we can do it once. And we will get the commit message for refactoring in all files.
In this case I am just trying to avoid the mess up like on #1374 for sklearnex/_device_offload.py and tests/run_examples.py

[samir-nasibli]

/intelci: run

[samir-nasibli]

I am going to do changes in each of sklearnex and onedal module py files: refactoring testing, dpnp integration and I will touch each py file for the algo and utils, so that's why I need codestyle it before. I think further PRs will be mess up with code formatting in other case.

[Vika-F]

I have not reviewed all 200+ files.
But I think the changes are good as soon as they made by automated code formatting tool and passed the testing.
Let those go to master.