Updated packager key of ainola
<!--
This template is used when a new packager PGP public key needs to be added to
the distribution's keyring.
It is either used by the sponsor of a new packager or by an existing packager
when adding a new key for themself.
-->
<!--
Please do not remove the above quick actions, which automatically label the
issue and assign relevant users.
-->
# Add a new packager key
## Details
- Username: @ainola <!-- MODIFY: Add the @-prefixed username -->
- PGP key ID: BE2DBCF2B1E3E588AC325AEAA06B49470F8E620A <!-- MODIFY: Add the "long format" key ID of the new PGP public key here -->
- Sponsors: @dvzrv <!-- MODIF[clearsigned_details.asc](/uploads/61d238e975d7d8725e2bd8a985941d05/clearsigned_details.asc)Y: Add the @-prefixed usernames of the sponsors -->
This key has already been signed against brett@i--b.com, which has been my UID for packaging. As we're moving under the domain of archlinux.org I have added ainola@archlinux.org as another UID to the same key. The key has been updated on Ubuntu's SKS.
<!--
NOTE: Attach the above information as a clearsigned document to this ticket.
https://www.gnupg.org/gph/en/manual/x135.html
If this is the key of a new packager, one of their sponsors needs to do the
signature.
If this is a new key of an already existing packager, the packager themself
needs to do the signature.
-->
## Checks
### New key owner
- [X] The [workflow for adding a new packager
key](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/workflows/add-a-new-packager-key)
has been followed
- [X] The key pair contains one user ID with a valid `<username>@archlinux.org` email address
used for signing
- [X] The key pair has been validated according to the [best
practices](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair)
- [X] The data in the [Details](#details) section is attached to this issue as
a clearsigned document
- [X] The public key has been uploaded to the SKS infrastructure
### Main key holders
- [x] The public key has been validated according to the [best
practices](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair)
- [ ] The public key has been signed by all main key holders
- [ ] @allan
- [ ] @anthraxx
- [x] @bluewind
- [x] @dvzrv
- [x] @pierre
### Keyring maintainer
- [ ] The public key contains one user ID with a valid
`<username>@archlinux.org` email address used for signing
- [ ] The public key has been validated according to the [best
practices](https://gitlab.archlinux.org/archlinux/archlinux-keyring/-/wikis/best-practices#validating-a-key-pair)
- [ ] The data in the [Details](#details) section is correct and signed with a
valid and trusted packager key, which is part of `pacman-key`
issue