feat: Updates copyright in conf.py

[darigovresearch]

Relevant to #69

[waldyrious]

It is usually unnecessary to add a year range to copyright notices; the date of original publication suffices. There are several publications online about this — here's one that offers detailed reasoning for this stance: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-not-bump-the-year-on-change

[darigovresearch]

@ezio-melotti & @waldyrious thanks for the review & the feedback.

Will leave this here in case a maintainer wants to merge it

[joshuaboys]

It is usually unnecessary to add a year range to copyright notices; the date of original publication suffices. There are several publications online about this — here's one that offers detailed reasoning for this stance: https://matija.suklje.name/how-and-why-to-properly-write-copyright-statements-in-your-code#why-not-bump-the-year-on-change

The date range as proposed is accurate for publications (such as a webpage) and I would argue that the project given it compiles to a webpage should contain the range.