[ENH] add test for all_objects tag filtering

[arnavk23]

Reference Issues/PRs

Fixes #162

What does this implement/fix? Explain your changes.

Added a unit test to test_lookup.py that creates a temporary package with a class that has a tag and asserts all_objects(..., filter_tags=...) returns it.

Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

• I've reviewed the project documentation on contributing
• I've added myself to the list of contributors.
• The PR title starts with either [ENH], [CI/CD], [MNT], [DOC], or [BUG] indicating whether
  the PR topic is related to enhancement, CI/CD, maintenance, documentation, or a bug.

For code contributions

• Unit tests have been added covering code functionality
• Appropriate docstrings have been added (see documentation standards)
• New public functionality has been added to the API Reference

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 83.33%. Comparing base (306958d) to head (921e521).
⚠️ Report is 177 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #474      +/-   ##
==========================================
- Coverage   85.07%   83.33%   -1.74%     
==========================================
  Files          45       52       +7     
  Lines        3015     3889     +874     
==========================================
+ Hits         2565     3241     +676     
- Misses        450      648     +198     

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

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fkiraly]

Thanks!

Could you kindly explain whether this causes any permanent side effects to the module structure? (if not, why not)

[arnavk23]

Thanks!

Could you kindly explain whether this causes any permanent side effects to the module structure? (if not, why not)

This PR is non-invasive with respect to the module structure. It just improves coverage of tests, which only affects testing environments and development workflows, not the operational code structure itself.