Update License/Copyright to 2025

[RodrigoVillar]

Goodbye 2024, Hello 2025!

[joshua-kim]

Not sure why our linter doesn't catch this (probably because the linter runs against the code on master instead of the commit on the branch) but we'd also have to update the headers in the code themselves.

➜  hypersdk git:(goodbye-2024) grep -r 'Copyright (C) 2024' . -l | wc -l
     401

[LitoMore]

This year means the year when the license starts. It is wrong to modify it.

The year of first publication of the work; in the case of compilations, or derivative works incorporating previously published material, the year date of first publication of the compilation or derivative work is sufficient.

See https://opensource.stackexchange.com/questions/5778/why-do-licenses-such-as-the-mit-license-specify-a-single-year

[joshua-kim]

If we're following that standard, we already already broke it in this prior commit because hypersdk started in 2023 IIRC. With that being said, we don't use a "standard" license (bsd/mit/et al.) and use a proprietary Avalanche "Ecosystem" license so I'm not sure if this same standard applies.

Concretely, the referenced law @LitoMore linked suggests that we should be marking 2023 as the start year irrespective of what license we're using in the LICENSE file, while the license headers found at the top of our sources files would just have their end years updated.

[LitoMore]

BTW, here is the context of why I noticed this pull request:

• https://github.com/orgs/community/discussions/148296

[RodrigoVillar]

For reference, I referred to the following PR for convention: ava-labs/avalanchego#2624