[stubby,getdns]: Remove maintainer from stubby and getdns packages

[jonathanunderwood]

Maintainer: me
Compile tested: N/A
Run tested: N/A

Description:
@neheb persists in merging PRs without package maintainer notification and approval. I have raised this previously, but this behaviour persists. A recent PR was merged which lacks the relevant documentation updates, and with problems that should have been addressed during review, and I am not prepared to pick up the mess and continue to maintain packages when a key maintainer does not follow process.

[jonathanunderwood]

History behind this:

• getdns: Fix typo in cmakeconfig.h.in files #14591 - PR submitted without boiler plate, so package maintainer not notified. @neheb merged without package maintainer approval. Package maintainer asked @neheb to not merge PRs that didn't follow process and complete the PR boilerplate and notify the maintainer.
• Bump getdns/stubby to 1.7.0 and 0.4.0 respectively #15808 - PR submitted without boiler plate, so package maintainer not notified. @neheb did tag package maintainer in PR, but then merged before maintainer had tested and approved the PR. Multiple problems with the PR: missing documentation update, build failures (stubby: fails to build #15843).
• stubby: remove libidn2 and libunwind dependencies #15837 - PR submitted by @neheb with an incorrect fix to build failures from Bump getdns/stubby to 1.7.0 and 0.4.0 respectively #15808. PR boilerplate not used, package maintainer not notified. PR merged by @neheb (submitter of PR) without review from package maintainer. Total breakdown of segregation of duties.

So, at this point, there's literally no point having package maintainers spending time on due diligence, as @neheb is just doing as he pleases, and failing to follow process everywhere.

[diizzyy]

I apologize and fully understand your reasoning. I've tried to get a discussion going of implementing rules and structure similar to FreeBSD's Ports Tree (outlined in FreeBSDs Porters Handbook) or alternatives to prevent issues such as this but it's hard to get things moving unfortunately.