AUR orphan request automation

Summary

One of the duties assigned to Trusted Users is the handling of AUR reports that come in. The majority of these are orphan requests due to inactive maintainers. We have to wait 14 days before accepting such a request, and they're often left behind because of this waiting period. I'm proposing some sort of automated system by which orphan requests get accepted after 14 days if the current maintainer does not contest it.

Motivation

Going through the deletion and merge requests is fairly easy as they can be accepted or closed right away, while orphan requests tend to be forgotten. The main way for AUR maintainers to state they're "still active" is with an email reply to the auto-generated ticket for the request, but going back and checking the mail archives to find those for verification is too cumbersome.

Specification

This would require changes to accept the requests automatically as well as give the current maintainers a way to close them. In the aurweb interface, current maintainers would have the ability to see open requests for packages they maintain, as well as the option to close them like a TU can.

One edge case to consider would be if the AUR maintainer claims to be active (by closing the request) but continues to let the package linger at an older version. In those situations, a TU could still step in to resolve it manually.