Help Needed: Version Control and CI/CD for AEP?

Hey there, AEP community! 

We're scratching our heads over here, trying to figure out the best way to manage our Adobe Experience Platform (AEP) configurations across our different environments. You know, the usual suspects - DEV, SIT, UAT, and PRD.

We've got this idea of using version control and maybe even setting up a CI/CD pipeline for our AEP stuff, but... we're not really sure if that's even a thing with AEP. 

So, we thought we'd reach out to you folks for some guidance. Here's what we're wondering:

1. Is version control for AEP configurations (like schemas, datasets, segments, configurations) actually doable (or recommended)?
2. Has anyone managed to set up a CI/CD pipeline for AEP? If so, how did you do it?
3. Are there any tried-and-true methods for juggling AEP configurations between environments?
4. What kind of gotchas should we watch out for if we try to go down this road?
5. If full-on CI/CD is a pipe dream, what other options might we have?

We're currently using GitLab (as version control and CI/CD) for our other projects (non Adobe), so we're kind of eyeing it for this too. But hey, we're totally open to whatever works best with AEP!

If you've got any nuggets of wisdom, war stories, or even just a "yeah, we tried that once" to share, we'd be super grateful. We're all ears!

Thanks a bunch for any help you can throw our way. You folks rock!