Fix warning

[mavaylon1]

Motivation

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

Fixed the warning regarding the TermSetWrapper being already wrapped. This shouldn't be raised when a configuration is not loaded.

How to test the behavior?

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

Checklist

• Did you update CHANGELOG.md with your changes?
• Does the PR clearly describe the problem and the solution?
• Have you reviewed our Contributing Guide?
• Does the PR use "Fix #XXX" notation to tell GitHub to close the relevant issue numbered XXX when the PR is merged?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 88.71%. Comparing base (d390c14) to head (c695bd2).

Additional details and impacted files

@@           Coverage Diff           @@
##              dev    #1116   +/-   ##
=======================================
  Coverage   88.71%   88.71%           
=======================================
  Files          45       45           
  Lines        9760     9760           
  Branches     2771     2771           
=======================================
  Hits         8659     8659           
  Misses        779      779           
  Partials      322      322           

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

[mavaylon1]

Review Notes:
This is a possible fix to #1079. However, the pydantic error is not showing up anymore. I am going to wait to see the output of manually running run_all_tests

Update: It seems to work.

[stephprince]

The container changes look good to me. What was the reason for removing the .yaml files?

[mavaylon1]

The container changes look good to me. What was the reason for removing the .yaml files?

They don't really need to be there since they can be generated when running the documentation.

[stephprince]

Got it, would it make sense to add them to the .gitignore then if they are generated by the docs?

[mavaylon1]

Got it, would it make sense to add them to the .gitignore then if they are generated by the docs?

Done. The failing hdmf-zarr test is also on schedule and seems to be unrelated to this PR.