ignore fact creation timestamp comparison in scheduling unit test

[uruwhy]

Description

tests/api/v2/handlers/test_schedules_api.py:183 would often fail due to a race condition where a fact creation date would be off by 1 second from the expected value. This fix replaces the expected creation date with a mock placeholder catch-all to avoid this issue, since the fact creation date is not part of the unit test criteria.

Type of change

• Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

Ran test via workflow

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code
• I have made corresponding changes to the documentation
• I have added tests that prove my fix is effective or that my feature works

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[Copilot]

Pull Request Overview

This PR fixes a race condition in a scheduling unit test where fact creation timestamps could differ by 1 second from expected values, causing intermittent test failures. The fix uses a mock placeholder to ignore timestamp comparisons since the creation date is not part of the test criteria.

• Replaces specific timestamp expectations with mock.ANY for fact creation dates
• Prevents race condition failures in test assertions
• Maintains test integrity by only ignoring non-essential timestamp data

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}