[Bug]: Generating a different version of NWB schema can cause class-level conflict errors

[ehennestad]

What happened?

Following up on discussion/question in #703 (comment)

Is there a way to detect this version change and clear specifically the classes causing the problem?

@bendichter I have explored this and although the MATLAB documentation seems to suggest that it is possible to clear specific classes, I don't manage to make this work in practice.

Also, MATLAB will update class definitions in memory when they are updated in file, but for some reason this does not work perfectly when regenerating MatNWB type classes. It might be because a full set of classes and superclasses are generated in one go, but it is very difficult to pinpoint. Maybe something to bring up with MathWorks

Steps to Reproduce

runtests('tests.unit.nwbReadTest/readFileWithIncompatibleVersion')

Error Message

N/A

Operating System

macOS

Matlab Version

All releases

Code of Conduct

• I agree to follow this project's Code of Conduct
• Have you ensured this bug was not already reported?

[ehennestad]

Idea: Generating type classes for different NWB format versions into separate namespaces, e.g
types.v270.core.NWBFile etc

Question: Is that going to be straight forward when taking extensions into account?