Fix explicit +/- signs in relative date offsets

[serhii73]

Close #1299

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 96.62%. Comparing base (920d725) to head (ec3a65e).
⚠️ Report is 2 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1303      +/-   ##
==========================================
+ Coverage   96.60%   96.62%   +0.01%     
==========================================
  Files         235      235              
  Lines        2889     2905      +16     
==========================================
+ Hits         2791     2807      +16     
  Misses         98       98              

☔ 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.

[Copilot]

Pull request overview

Fixes parsing of relative date expressions containing explicit +/- time offsets (e.g., "yesterday +1h"), addressing issue #1299.

Changes:

• Updated FreshnessDateDataParser to recognize signed numeric quantities (e.g., +1 hour, -30 minutes) and apply them correctly.
• Added regression tests validating "yesterday"/"tomorrow" +/- <offset> parsing behavior via dateparser.parse().

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.

File	Description
dateparser/freshness_date_parser.py	Extends unit parsing regex to accept +/- and adjusts relativedelta application to respect explicit signs.
tests/test_date_parser.py	Adds parameterized coverage for "yesterday"/"tomorrow" +/- offsets plus targeted regression assertions.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.