docs: Updates copyright year

[frgfm]

This PR updates the year in copyright notices in all python files.

[codecov[bot]]

Codecov Report

All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0ffbf38) 94.95% compared to head (6c684b5) 94.95%.

Additional details and impacted files

```diff @@ Coverage Diff @@ ## main #311 +/- ## ======================================= Coverage 94.95% 94.95% ======================================= Files 63 63 Lines 1505 1505 ======================================= Hits 1429 1429 Misses 76 76 ``` | [Flag](https://app.codecov.io/gh/pyronear/pyro-api/pull/311/flags?src=pr&el=flags&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pyronear) | Coverage Δ | | |---|---|---| | [unittests](https://app.codecov.io/gh/pyronear/pyro-api/pull/311/flags?src=pr&el=flag&utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pyronear) | `94.95% <ø> (ø)` | | Flags with carried forward coverage won't be shown. [Click here](https://docs.codecov.io/docs/carryforward-flags?utm_medium=referral&utm_source=github&utm_content=comment&utm_campaign=pr+comments&utm_term=pyronear#carryforward-flags-in-the-pull-request-comment) to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

[MateoLostanlen]

Hi @frgfm , thanks for the PR. I find it a bit absurd that we have to do this every year, isn't there another way of structuring the header?

[frgfm]

Unfortunately, the alternative is to remove this altogether but if the range expires, then we have a problem. I've checked online and cannot find an unending year range for copyright notice so far :man_shrugging:

On the commit history it looks like there is a lot but to be honest, changing that every year is rather easy (find & replace in the entire project)