Update license copyright year(s)

[github-actions]

No description provided.

[agriyakhetarpal]

I think auto-merge won't work because we need CI to run because of required checks (which, again, sounds wasteful to me and to the environment in the way they have been configured right now)

[arjxn-py]

I think auto-merge won't work because we need CI to run because of required checks (which, again, sounds wasteful to me and to the environment in the way they have been configured right now)

i see, then i'll come back to it once CI is happy

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 99.22%. Comparing base (a7253b8) to head (cef4318).
Report is 16 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #4727      +/-   ##
===========================================
- Coverage    99.22%   99.22%   -0.01%     
===========================================
  Files          303      303              
  Lines        23070    23101      +31     
===========================================
+ Hits         22891    22921      +30     
- Misses         179      180       +1     

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

[agriyakhetarpal]

FYI, while we've done this now, the consensus apparently is that it is no longer needed to continue to update the copyright years for the recipe. Here are some references:

• https://hynek.me/til/copyright-years/
• Use static copyright years python/cpython#126133 (comment)

So, it should be fine to drop this workflow altogether – it's all the more better for our CI if we keep our workflows maintainable and drop unneeded workflows.