Update matio for MSL 4.1.0

[casella]

Following the discussion in #4480, I think we should update matio in MSL 4.1.0 to the latest version, to avoid shipping a library with known vulnerabilities. The latest version of matio merged into MSL 4.1.0 was 1.5.24, November last year.

MSL 4.1.0 misses the two latest updates, 1.5.26, which was merged on master on March 28 in #4285 but not back-ported to main/4.1.x, and 1.5.27. If we merge them on maint/4.1.x, we should also re-build the matio binary, since we agreed to still ship the binaries with the MSL for 4.1.0.

Considering the delay in releasing 4.1.0, due to the awkward regression testing process, I think there's no reason to not include them in the 4.1.0 release. We are still not done with regression testing, and the likelyhood that this update introduces some new regressions is very small, so that's not going to be disruptive.

@beutlich what do you think? Could you prepare a PR which updates matio and the matio binaries to 1.5.27 on maint/4.1.x?

If we see that it causes regressions, we can always roll it back.

[beutlich]

#4455 is the appropriate PR for master. EDIT: superseded by #4497. This is just the sources, not the binaries, because there still is #4347 open.

[casella]

@beutlich do you think you can provide the binaries for MSL 4.1.0? Otherwise, we'll keep whatever version of MatIO we had when you last built the binaries.

[beutlich]

Can do, but which branch or which PR?.

[casella]

In 4.1.0 we decided to still keep the compiled binaries in the git repo. As I understand this would require to

• merge Update matio library to 1.5.28 #4497
• backport it to maint/4.1.x
• recompile the relevant binaries and commit them to the Resources directory

But maybe I missed the point of your question?