Add fully configured image for MATLAB 2025b

[aranega]

Summary

Upgrades the MATLAB image to target MATALAB 2025b, iterating on the MATLAB for Nebari base Dockerfile created by @asmacdo in #283 .

What's Changed

• Re-introduction of Python dependencies and tooling for the interaction with the MATLAB toolboxes using Python as backend
• Re-introduction of MATLAB official toolboxes as defined in the manifest with the addition of some necessary toolboxes dependencies
• Re-introduction of the Deep Learning Toolbox Converter for TensorFlow Models
• Re-introduction of the third-party libraries with adequate version as defined in the manifest, with exception of matNWB which have been pinned to 2.9.0 because of an apparent regression introduced in 2.10.0 which breaks the live-script examples.
• Cleaning of some Python dependencies
• Change the way the dandi-io library is installed as it relies on a dependency that is not supported for Python >= 3.13
• Remove the ENTRYPOINT as described in Replace legacy images with Nebari-compatible images #283 to let the startup process to Nebari

[kabilar]

Thanks for the contribution, @aranega.

Hi @asmacdo, could you please review this when you have a chance? Thanks.

[asmacdo]

This is great! Looks like the github runner was sufficient too, so we can avoid private repo/external runners complexity!!

This is going to be merged into my PR branch, so we will have another change to review more carefully before it goes live. That said, it all looks reasonable to me.

@aranega regarding the python deps, are they needed for the toolboxes? Maybe we could install from a matlab-requirements.txt with comments for why specific deps are needed, (especially when version requirements specified).

[aranega]

@aranega Some are necessary for the tensorflow/keras models toolbox, and others for the dandi-io librariy, but some others were here historically here and I was afraid to break something I couldn't see directly by removing them. I can try to trim more and keep somewhere what I removed in case an error comes back later to have a log of what might be the solution.

Got it for the matlab-requirements.txt file, I'll do both (requirement file and more trimming) asap!

[asmacdo]

I'd be fine with leaving trimmed requirements in the file commented out

[satra]

feel free to limit dependencies to matlab and dandi joint use cases. no need to consider all possible uses. we are trying to move to specific images.

[aranega]

@satra @asmacdo Thanks for the feedback! I trimmed the python dependencies to the bare minimum, and I didn't see any weird behavior when executing the live-script examples. I let commented in the matlab-requirements.txt file the packages that were originally here in case we have a bad surprise later.