MATLAB External Source Control Integration does not use VSCode MATLAB session

[gohma231]

Is your feature request related to a problem? Please describe.
When launching the simulink difftool via command-line (see [1]), a new session of MATLAB is opened rather than the existing session of MATLAB used by VSCode.

This is not useful as this means paths are not setup appropriately and it results in missing subsystem references.

[1] https://www.mathworks.com/help/matlab/matlab_prog/customize-external-source-control-to-use-matlab-for-comparison-and-merge.html

Describe the solution you'd like
When launching the simulink difftool via command-line, the existing instance of MATLAB used by VSCode would be used to avoid opening a new MATLAB process.

Example command using the mlDiff definition in [1]: git difftool --no-prompt -t mlDiff origin/master -- Model/fileA.slx

Describe alternatives you've considered
Opening MATLAB separate from VSCode works without issue.