TermSet minor test updates, _repr_html_, name field

[mavaylon1]

Motivation

What was the reasoning behind this change? Please explain the changes briefly.

• Add repr_html to Termset
• Add name to Termset
• Update tests to include name

How to test the behavior?

Show how to reproduce the new behavior (can be a bug fix or a new feature)

Run notebook for html representation and then the unit tests.

Checklist

• Did you update CHANGELOG.md with your changes?
• Have you checked our Contributing document?
• Have you ensured the PR clearly describes the problem and the solution?
• Is your contribution compliant with our coding style? This can be checked running ruff from the source directory.
• Have you checked to ensure that there aren't other open Pull Requests for the same change?
• Have you included the relevant issue number using "Fix #XXX" notation where XXX is the issue number? By including "Fix #XXX" you allow GitHub to close issue #XXX when the PR is merged.

[mavaylon1]

Fix #893

[mavaylon1]

It's been a while since #893 but we don't have versions anymore, the prefixes can be called by "termset.sources", I added the name, I added repr_html

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Comparison is base (75c686a) 88.59% compared to head (42488be) 88.65%.

Additional details and impacted files

@@            Coverage Diff             @@
##              dev     #967      +/-   ##
==========================================
+ Coverage   88.59%   88.65%   +0.06%     
==========================================
  Files          45       45              
  Lines        9424     9451      +27     
  Branches     2684     2688       +4     
==========================================
+ Hits         8349     8379      +30     
+ Misses        760      757       -3     
  Partials      315      315              

Files	Coverage Δ
src/hdmf/term_set.py	98.23% <100.00%> (+2.43%)	⬆️

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[mavaylon1]

I did not move termset and herd to a folder as the issue ticket suggested. That would require a lot of import changes for something that doesn't provide much value to the user, nor me as the main person who works on this.

[rly]

The YAML schema in TermSet.term_schema_path already has a name. I think it is required but I am not sure. Could we extract the name field from the schema? I think that is what I meant in #893. Add convenience properties name, version, and prefixes that allow the user to get those values from the YAML schema.

[mavaylon1]

The YAML schema in TermSet.term_schema_path already has a name. I think it is required but I am not sure. Could we extract the name field from the schema? I think that is what I meant in #893. Add convenience properties name, version, and prefixes that allow the user to get those values from the YAML schema.

That makes sense to extract.

[rly]

@mavaylon1 thanks for the PR. I think printing "[item 1] [item 2] ... [item 3]" and "[item 1] [item 2] ... [item 3] [item 4]" when there are only 3 or 4 items in the list is misleading, so I changed the format a bit so that the ellipses only show up if there are more items present than are shown. Super minor, but I think it is better this way.

Also, the panda that you added to your example is a genus, not a species, so I updated that accordingly.