add full apache license

[lsmith77]

What do these changes do?

This is a follow-up to #7048, to fix license detection by GitHub.

It seems like the boilerplate isn't meant to be used a the license but rather within source code file:
licensee/licensee#393

Are there changes in behavior for the user?

Fix incorrect use of the Apache 2.0 license, which also means that GitHub can now properly detect the license.

Related issue number

N/A

Checklist

N/A

[lsmith77]

FYI this also should be done in other repos:

• https://github.com/aio-libs/async-timeout/blob/master/LICENSE
• https://github.com/aio-libs/aiohttp-session/blob/master/LICENSE
• https://github.com/aio-libs/aiodocker/blob/master/LICENSE
• https://github.com/aio-libs/multidict/blob/master/LICENSE
• https://github.com/aio-libs/aiohttp-sse/blob/master/LICENSE
• https://github.com/aio-libs/yarl/blob/master/LICENSE
• https://github.com/aio-libs/sort-all/blob/master/LICENSE
• https://github.com/aio-libs/aiohttp-demos/blob/master/LICENSE
• ..

Note it is done properly in the following repos:

• https://github.com/aio-libs/aiosmtpd/blob/master/LICENSE
• https://github.com/aio-libs/aiohttp-security/blob/master/LICENSE
• https://github.com/aio-libs/aiosignal/blob/master/LICENSE
• https://github.com/aio-libs/frozenlist/blob/master/LICENSE
• https://github.com/aio-libs/aiohttp-cors/blob/master/LICENSE
• ..

[lsmith77]

Apparently this can confuse licensee
licensee/licensee#554

[codecov]

Codecov Report

Merging #7049 (a6632df) into master (12f56d7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #7049   +/-   ##
=======================================
  Coverage   97.50%   97.50%           
=======================================
  Files         103      103           
  Lines       29972    29972           
  Branches     3640     3640           
=======================================
  Hits        29224    29224           
  Misses        567      567           
  Partials      181      181           

Flag	Coverage Δ
CI-GHA	97.40% <ø> (ø)
OS-Linux	97.04% <ø> (-0.01%)	⬇️
OS-Windows	95.39% <ø> (ø)
OS-macOS	96.68% <ø> (-0.01%)	⬇️
Py-3.10.8	97.21% <ø> (-0.01%)	⬇️
Py-3.11.0	96.55% <ø> (ø)
Py-3.11.0-rc.2	?
Py-3.7.15	96.88% <ø> (ø)
Py-3.7.9	95.27% <ø> (ø)
Py-3.8.10	95.17% <ø> (ø)
Py-3.8.14	96.78% <ø> (ø)
Py-3.9.13	95.16% <ø> (ø)
Py-3.9.14	96.57% <ø> (ø)
Py-3.9.15	96.76% <ø> (-0.05%)	⬇️
Py-pypy7.3.9	96.43% <ø> (-0.01%)	⬇️
VM-macos	96.68% <ø> (-0.01%)	⬇️
VM-ubuntu	97.04% <ø> (-0.01%)	⬇️
VM-windows	95.39% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

[Dreamsorcerer]

Thanks, looks good to me. I think @asvetlov usually updates these kind of things with a tool that can update all our repositories in one go. Not sure what it is though...