test(warnings): switch from the unmaintained pytest-freezegun to pytest-freezer removing warnings

[noirbizarre]

Description

Switch from pytest-freezegun which is not maintained anymore and stuck on a legacy freezegun version raising lots of warnings to pytest-freezer its maintained fork by the official pytest-dev github organization which is maintained and up to date, raises no warnings and provide typing.

Checklist

• Add test cases to all the changes you introduce
• Run ./scripts/format and ./scripts/test locally to ensure this change passes linter check and test
• Test the changes on the local machine manually
• Update the documentation for the changes (N/A)

Expected behavior

No behavior change expected.
Test should still pass but the 2662 warnings raised should have disappeared.

Steps to Test This Pull Request

Run the test suite

Additional context

Dependency change so the dependencies have been re-locked

[codecov]

Codecov Report

❗ No coverage uploaded for pull request base (v3@489096b). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files

@@ Coverage Diff @@## v3 #639 +/- ##
=====================================
Coverage ? 98.42% =====================================
Files ? 39 Lines ? 1655 Branches ? 0 =====================================
Hits ? 1629 Misses ? 26 Partials ? 0 

Flag	Coverage Δ
unittests	98.42% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report at Codecov.
📢 Do you have feedback about the report comment? Let us know in this issue.

[Lee-W]

Thanks @noirbizarre !

@woile I'm planning on merging it this week. Let me know if you want to take a deeper look. Thanks!

[Lee-W]

@noirbizarre I'm thinking maybe we could send this PR directly to main instead of v3. We could rebase it back to v3 later. What do you think?

[noirbizarre]

Except for the lockfile part, it can be sent to main. But in case of rebase or merge on v3, lockfile should be updated (they will conflict).

[Lee-W]

I think we can do the relock for main and relock again after rebasing to v3. What do you think?

[noirbizarre]

I say that because we don't have a lock yet on main so it will be a 2 step move:

• merge the pyproject.toml change only on main
• relock on v3 on rebase/merge
  I don't have the proper permissions to do it but I can just cherry-pick and amend the pyproject.toml part on main and keep this PR for v3, merge will be easier I think

[noirbizarre]

Backported in #643 but I realised that given test fixes are not on master tests are not passing on master

[Lee-W]

I just merge #643 back to main. Once main is updated, you can update your local main and rebase it back to your feature branch and than force push to this branch. Thanks for the prompt PR!

[noirbizarre]

Thanks !
Given I can't rebase v3, I just merged main into this branch so it won't conflict on later merges.

[Lee-W]

indeed. I forget that 😱 let me do so now!

[noirbizarre]

Thanks, updated.

But I think your working copy was not up to date and #638 is missing from the rebased v3 (It should not conflict with this PR so you can cherry-pick it on v3 before or after this PR merge without any issue)

[Lee-W]

yep.... do you still have the branch on your local?

[noirbizarre]

No but I just restored it on github in the PR #638

[Lee-W]

ah yes, we could do that. I just push that back to v3

[noirbizarre]

And this is properly rebased on v3
(I kept the style change in a separate commit: it was changed in the previous commit and I believe black was not up to date)