Add AlignedDynamicTable non-generated base class with category table validation

[ehennestad]

⚠️ Depends on #836 — merge that first

Motivation

The AlignedDynamicTable schema defines two requirements in docstrings that cannot be enforced by the generated class alone:

1. All sub-tables added to an AlignedDynamicTable "MUST have the same number of rows" (source).
2. The names in the categories property MUST match the names of category tables in the AlignedDynamicTable (source).

Without additional runtime validation, users can create invalid NWB files when using AlignedDynamicTable or its subtypes.

This PR adds validation hooks for AlignedDynamicTable through a custom base class. It also adds convenience APIs so valid tables are easier to construct: schema-defined category tables auto-register in categories when assigned, and custom category tables can be added with addCategory(name, table).

This PR stacks on #836 and uses its schema validation reporting context to maintain backwards-compatibility by making AlignedDynamicTable validation on construction warn instead of error to ensure pre-PR icephys tutorial examples can still run without breaking.

Example usage (updated snippets from icephys tutorial)

1. categories do not need to be listed when the table is initialized with rows — assigning a category table later registers it automatically:

% before
ic_rec_table = types.core.IntracellularRecordingsTable( ...
    'categories', {'electrodes', 'stimuli', 'responses'}, ...  % name is manually added to categories
    'colnames', {'recordings_tag'}, ...
    'id', types.hdmf_common.ElementIdentifiers('data', int64([0; 1; 2])), ...
    'recordings_tag', ...);
ic_rec_table.electrodes = ...;   % table is assigned afterwards

% after
ic_rec_table = types.core.IntracellularRecordingsTable( ...
    'colnames', {'recordings_tag'}, ...
    'id', types.hdmf_common.ElementIdentifiers('data', int64([0; 1; 2])), ...
    'recordings_tag', ...);
ic_rec_table.electrodes = ...;   % auto-registers in name `categories`

2. Use addCategory for custom categories instead of the manual two-step:

% before
ic_rec_table.categories = [ic_rec_table.categories, {'recording_lab_data'}];
ic_rec_table.dynamictable.set('recording_lab_data', customTable);

% after
ic_rec_table.addCategory("recording_lab_data", customTable);

How to test the behavior?

runtests('+tests/+system/AlignedDynamicTableTest.m')

Checklist

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

🤖 Generated with Codex