How run-modes are supported for CONGA Environments for AEM Cloud?

you're welcome

Thanks for clarifying Sure, I’ll keep the mailing list in mind. This time I didn’t know. That’s all the doubt I had regarding the topic. Please feel free to mark is as “fixed“!

yes, the concepts of the cloud manager and how deployment works with it put some sort of limitation to the flexibility of CONGA concerning the environments (unless you have multiple AEMaaCS programs, there you could have different environment files for each program - but you might have to license them individually).

for OSGi configurations it's as you describe: within the template generating the OSGi "provisioning" configurations you can apply the run modes within the templates. please be aware that the syntax for multiple run modes is a bit differently, separated by "," (see docs)

and you're right, currently this may lead to duplication of the configuration definitions in the template if you need different actual values e.g. for dev, stage and prod.

keep in mind that adobe has a different concept for applying environment-specific configurations in CM: environment variables. this is also helpful for managing secrets, what we did with ansible vaults and encrypting during build for AEM crypto service, which is also no longer supported in AEMaaCS. the values defined in environments variables can be references in the OSGi configuration:
https://experienceleague.adobe.com/docs/experience-manager-cloud-service/implementing/deploying/configuring-osgi.html?lang=en

we currently do not have any tooling in place to manage the values of environment variables in some sort of declarative way manged from a central git repository, it's cumbersome to manage them manually via aio plugins on the command line.

p.s. when you have topics that are more questions then actual issues our mailing list is a good place to start: https://wcm.io/mailing-lists.html