If something that relies on say, one of their log services, and that log service is getting end-of-lifed then all the dependent services that aren't really critical will also get shutdown. It's a forcing mechanism to keep the amount of cruft down. If that service that relies on the old service is that important they'll put the resources on the project long enough to port it to the new service.

It doesn't need to stay up to date with an evolving stack

Static files in Google's equivalent of an S3 bucket with public downloads enabled, that's it.

By design these types of blob storage services "just work" as a consumer indefinitely (otherwise there wouldn't be much of a point to them)

-

I get the whole "who does it get billed to, who's going to take a day to write this script that makes the preview page" deal, but like, this is literally the one time where just a little bit of initiative can win some brownie points with minimal investment, can't they do it?