[CI][MATLAB] Hard-code `release` to `R2023a` for `matlab-actions/setup-matlab` action in MATLAB CI workflows

[kevingurney]

Describe the bug, including details regarding any error messages, version, and platform.

Due to a recent change to default to R2023b by default for the [matlab-actions/setup-matlab](https://github.com/matlab-actions/setup-matlab) action in GitHub Actions, the MATLAB CI workflows are failing.

Example failure logs:

https://github.com/apache/arrow/actions/runs/6250586979/job/16970596069?pr=37773#step:9:70

Our preferred solution to address this in the short term is to explicitly specify the release parameter to the setup-matlab action to be R2023a.

In the long term, we can work on figuring out why the build is failing on Windows with R2023b.

For reference - it appears that the FindMatlab CMake module only recently added R2023b to its list of recognized versions:

https://gitlab.kitware.com/cmake/cmake/-/merge_requests/8804

Component(s)

Continuous Integration, MATLAB

[kevingurney]

I'm actively investigating these failures now on https://github.com/mathworks/arrow/tree/GH-37805.

Most likely, I will just hard-code the release to R2023a for the time being.

[kevingurney]

Hard-coding the release to R2023a appears to resolve this issue:

https://github.com/mathworks/arrow/actions/runs/6251345588.

I'll create a PR for this.

[kevingurney]

I've opened PR #37808 to address this issue.

I've also created #37809 as a follow up to determine why the MATLAB workflows are failing on Windows when using MATLAB R2023b.