TEST: increase threshold for memory usage on tests

[david-cortes-intel]

Description

ref #2107

This PR increases the threshold for the tests that check for memory usage increases to 25% of the input data size, as those tests were previously producing failures on some CI runs in that other PR.

Regardless of whether there are or aren't any memory leaks, it is not guaranteed that this condition would be met, since a memory allocator is not required to return all memory to the OS after freeing it, but this increase should allow the CI jobs to pass until a better solution is found.

Note that the PR contains an unrelated change - this is coming from the precommit hook, which required that change to go into the PR.

---

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.

[samir-nasibli]

I think better to use this specific value for specific cases

[david-cortes-intel]

I think better to use this specific value for specific cases

Changed it use 25% for pandas inputs, while leaving it at 15% for other types of inputs.

[Alexsandruss]

Check PR Checklist / Close all checkboxes before moving from draft

[david-cortes-intel]

/intelci: run

[samir-nasibli]

Looks good! Assuming green internal CI as well.
For me make sense also cover with ticket further investigation the reason of such number increase