[overall tracking] Figure Out Which GAE Builtins to Keep Using

[phil-lopreiato]

So, seems like Google backtracked on this...

https://cloud.google.com/appengine/docs/standard/python/migrate-to-python3#services

Beginning in September 2021, App Engine allows apps in the Python 3 runtime to access some App Engine bundled services and APIs previously available only in the Python 2 runtime.

This is good news, because we can rip out a bunch of the janky compatibility shims we had to write. But unfortunate that we had to writ them in the first place.

A quick brainstorm from me and @ZachOrr on what we should do:

• memcache -> legacy bundled
• ndb -> new library, but do a janky import for write compatibility so I can delete my janky crap
• testbed -> legacy bundled, so I can delete my datastore implementation
• webserver -> stick with flask
• app_identity -> had no good replacement, keep using for the stuff we need (verifying the project ID in production)
• taskqueue -> I need to do some science, if we can get that stuff working locally without needing Redis, let’s drop my implementations
• urlfetch -> let’s keep using requests
• users -> We should stick with Firebase users except for things like admin auth validation - where we should continue to use Google (since it looks at the project IAM stuff)