Change: Only embed specs/namespaces for types that are included in NWB file on export

[ehennestad]

Fix #607

Motivation

Ensure that only relevant namespaces/specifications are embedded in an NWB file. This issue suggests that such extra namespaces can cause errors when validating with NWBInspector.

How to test the behavior?

Export NWB file with types from a subset of available extension and check the file's `specification` group

Questions / todo

• [x] Are namespace names always specified in kebab-case? - Appears so
• [x] Does matnwb always format namespace names as snake_case? - Appears so
• [ ] Should the specification group be completely cleared before rewriting it if exporting to an existing file?
• [x] Check superclasses of each type and included namespace of superclasses as well
• [ ] Add unit test

Checklist

• [x] Have you ensured the PR description clearly describes the problem and solutions?
• [x] Have you checked to ensure that there aren't other open or previously closed Pull Requests for the same change?
• [x] If this PR fixes an issue, is the first line of the PR description fix #XX where XX is the issue number?

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 91.00%. Comparing base (95b5e5e) to head (a458d62). Report is 1 commits behind head on master.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## master #615 +/- ## ========================================== + Coverage 90.90% 91.00% +0.09% ========================================== Files 107 107 Lines 4751 4768 +17 ========================================== + Hits 4319 4339 +20 + Misses 432 429 -3 ```

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.