prod -> main: pull hotfixes back into main

[johnwalz97]

Pull Request Description

What and why?

How to test

What needs special review?

Dependencies, breaking changes, and deployment notes

Release notes

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

Pull requests must include at least one of the required labels: internal (no release notes required), highlight, enhancement, bug, deprecation, documentation. Except for internal, pull requests must also include a description in the release notes section.

[github-actions]

PR Summary

This PR enhances the test loading mechanism by ensuring that every test function has defined __tags__ and __tasks__ attributes. If these attributes are absent, they are automatically initialized to empty lists. This change ensures consistency in how test metadata is handled and prevents potential errors when these attributes are accessed later in the testing workflow.

Test Suggestions

• Write tests that deliberately define test functions without __tags__ and __tasks__ to verify they are automatically set to empty lists.
• Validate that if a test function already has __tags__ or __tasks__ set, the existing values are preserved and not overwritten.
• Check the integration with the test registry to confirm that the attributes are correctly attached to the test functions after registration.