Updating copyright year to 2026 in docs configuration

[xiaobei0715]

No description provided.

[github-actions]

Thank you for your contribution to the Solidity compiler! A team member will follow up shortly.

If you haven't read our contributing guidelines and our review checklist before, please do it now, this makes the reviewing process and accepting your contribution smoother.

If you have any questions or need our help, feel free to post them in the PR or talk to us directly on the #solidity-dev channel on Matrix.

[cameel]

@czepluch I think we should change it to just 2016, The Solidity Authors so that we don't have to bump that every year. If not, we need a TODO somewhere to remember about it. What do you think? For some context, here's some earlier discussion: #14849.

[cameel]

BTW, in most files that do have copyright year we only have the initial year, but there are also have some files that do have the upper bound. And we don't seem to be updating those. I would remove the year from those too.

Examples:

solidity/scripts/docker/buildpack-deps/Dockerfile.ubuntu2404.arm

Line 22 in 9dc6b2e

# (c) 2016-2025 solidity contributors.

solidity/scripts/docker/buildpack-deps/Dockerfile.ubuntu2404

Line 22 in 9dc6b2e

# (c) 2016-2024 solidity contributors.

[czepluch]

@czepluch I think we should change it to just 2016, The Solidity Authors so that we don't have to bump that every year. If not, we need a TODO somewhere to remember about it. What do you think? For some context, here's some earlier discussion: #14849.

I would remove it entirely. From what I gather, there's no legal requirement to have it on a website and the thing that matters is the LICENSE file on the Github repo. Maybe we need to check with a legal entity to confirm. Fully removing it seems like the solution that requires the least maintenance in the future (none) and that creates the least confusion from people thinking the project is abandoned if it only shows 2016, the solidity devs.