TEST: Use deterministic seeds in tests

[david-cortes-intel]

Description

This PR modifies tests parameterized by non-deterministic seeds to use fixed seeds.

Having these randomly-determined seeds has the issue that it makes it hard to compare a specific test over several runs (e.g. for different configurations), in addition to making it harder to reproduce potential failures.

---

PR should start as a draft, then move to ready for review state after CI is passed and all applicable checkboxes are closed.
This approach ensures that reviewers don't spend extra time asking for regular requirements.

You can remove a checkbox as not applicable only if it doesn't relate to this PR in any way.
For example, PR with docs update doesn't require checkboxes for performance while PR with any change in actual code should have checkboxes and justify how this code change is expected to affect performance (or justification should be self-evident).

Checklist to comply with before moving PR from draft:

PR completeness and readability

• I have reviewed my changes thoroughly before submitting this pull request.
• 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.

Performance

Not applicable.

[samir-nasibli]

👍

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
github	83.18% <ø> (ø)

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

[icfaust]

@david-cortes-intel @samir-nasibli i wish i had been consulted on this change. 1) because I introduced this code and 2) the proper management of determism shouldn't rely on assumptions of the functionality of oneDAL (e.g. that default seeds exist for oneDAL) 3) if run to run determism is necessary for certain tests in multiple configurations we should be doing comparisons using only subsets of the tests. if this is with respect to another testing framework, we should define and publish requirements to those. Please note on the horizon it is planned to introduce fuzz testing (as an initiative). as a note, i do not think reverting is necessary, what is done is done (not a big deal)