This was actually the second time I stopped learning game development and it was for the exact same reason and at the exact same lesson; basically I was learning 2D game development, got to the stage where you set up the sprites and can decide how long each sprite lasts for (so perhaps one frame in a several frame long sequence you want that one sprite to last on the screen a little longer than the rest, you can), and also setting up each sprite and such, only to realize I'd have to do this for everything that has sprites and was like noooooooope.
Maybe if I ever try to learn game development again I'll just stick to ASCII games or something. I watch the game dev videos where people make games in a short amount of time, see all the work that goes into the stuff they do, and realize it's not for me.
I'm honestly way too lazy to do any of this stuff. I wanted to be a game developer ever since I was a kid, but I'm also infinitely lazier now than I was back then.
You can always try making something that doesn't require animated sprites. I haven't really spent much time working on games but the last time I was messing around in Godot I was making a system for placing rail tracks, and a terrain generation system. I didn't have to worry about making sprites at all, and all the stuff I wanted the player to place down was just static graphics that I was generating procedurally. Admittedly, later on I wanted to have the player place down buildings like train stations and generators that would probably have to be animated, but I think if you've already invested a lot of time into the fun part of a project it gets easier to do the boring parts.