https://www.mozilla.org/en-US/security/known-vulnerabilities...
The team that qualifies and does the release work for Thunderbird are volunteers. I believe that the builds are done on Mozilla hosted hardware.
The people who are making these complaints are disproportionately those who have no problem using Debian or Arch, so I don't think that's the crux of the issue for them.
Something is either being actively developed or it's dieing, there is no in between with software, there is no finished state.
I wish more pieces of software would get to the finished state and would slip into maintenance mode.
By the way - the IETF standardised an OAuth2 SASL mechanism (RFC 7628) a couple of years ago, no idea why GMail doesn't support it.
Basically, the only thing that is kind-of Gmail specific is the auth support (https://bugzilla.mozilla.org/show_bug.cgi?id=849540). If Gmail sometimes in future switches from OAuth2 to some other protocol, the client will have to be updated.
I don't understand why people are disappointed that Mozilla has stopped actively developing thunderbird - it means it's not going to change. There is an email client that you like, as is, and want to keep using, and you're annoyed because mozilla has promised not to change it?