Conflict between `actions/cache` and `setup-matlab@v2`

[mcafaro]

It looks like it may be possible to cause an issue in setup-matlab@v2 if you use the actions/cache action manually rather than the cache: true input.

See https://github.com/opt4ai/prima/actions/runs/7855964578/job/21438238878 for example. In this workflow, MATLAB is cached using actions/cache and setup-matlab@v2 is run with cache: false (default).

When this workflow runs, the cache is restored by actions/cache and setup-matlab@v2 skips claiming it found MATLAB in the cache (even though cache: false). run-command@v2 is then unable to find matlab on the system path.