MAINT: Add back catboost to conda jobs

[david-cortes-intel]

Description

The .yaml file for conda builds had removed catboost and shap as a test dependencies due to not working with numpy>=2. By now, the latest releases of both of those packages in conda-forge work with numpy>=2, so they can be added back as it says in the TODO line.

---

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.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Flag	Coverage Δ
azure	79.87% <ø> (ø)
github	71.96% <ø> (ø)

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[david-cortes-intel]

/intelci: run

[icfaust]

something is funky with the windows conda recipe numpy versioning with catboost :(

[david-cortes-intel]

@icfaust I don't see any difference in the packages being installed between this failed job here and the same job in the last commit to main:
https://dev.azure.com/daal/daal4py/_build/results?buildId=45854&view=logs&jobId=ec5c909d-198b-517a-c410-a3957b9d3571&j=ec5c909d-198b-517a-c410-a3957b9d3571&t=3b780943-6ec8-5eaa-4862-0514cc621c25
https://dev.azure.com/daal/daal4py/_build/results?buildId=45854&view=logs&jobId=ec5c909d-198b-517a-c410-a3957b9d3571&j=ec5c909d-198b-517a-c410-a3957b9d3571&t=3b780943-6ec8-5eaa-4862-0514cc621c25

Looks like it might be a sporadic failure, will try to rerun.