Pin mkl to avoid Windows unit test failures with version 2024.2.2 (release-next)

[thomashampson]

Description of work

A couple of unit tests (AbinsBroadeningTest and MuonMaxEntTest) starting failing on Windows for no apparent reason:
https://builds.mantidproject.org/view/Nightly%20Pipelines/job/main_nightly_deployment/907/testReport/
There is some output about dividing by zero, and mkl (a math library only in our Windows environments) has updated since the last successful run. It may be that there is a problem with our code, but for now we can pin mkl to the previously working version.

There is no associated issue.

To test:

Make sure the two offending tests run on Windows and pass.

This does not require release notes because it's a dependency pin

---

Reviewer

Please comment on the points listed below (full description).
Your comments will be used as part of the gatekeeper process, so please comment clearly on what you have checked during your review. If changes are made to the PR during the review process then your final comment will be the most important for gatekeepers. In this comment you should make it clear why any earlier review is still valid, or confirm that all requested changes have been addressed.

Code Review

• Is the code of an acceptable quality?
• Does the code conform to the coding standards?
• Are the unit tests small and test the class in isolation?
• If there is GUI work does it follow the GUI standards?
• If there are changes in the release notes then do they describe the changes appropriately?
• Do the release notes conform to the release notes guide?

Functional Tests

• Do changes function as described? Add comments below that describe the tests performed?
• Do the changes handle unexpected situations, e.g. bad input?
• Has the relevant (user and developer) documentation been added/updated?

Does everything look good? Mark the review as Approve. A member of @mantidproject/gatekeepers will take care of it.

Gatekeeper

If you need to request changes to a PR then please add a comment and set the review status to "Request changes". This will stop the PR from showing up in the list for other gatekeepers.

[robertapplin]

Code changes look good. Approving this because the real test is that it passes the Windows PR job