Collection Specific Environment Variables Superseding Active Environment Variables

As per [docs]( there are only 3 scopes for environment variables: folder, sub, and base (in order of priority). I propose that scoping environment variables at the Collection level has high value and a much needed feature that is missing. The use case for a Collection to utilize environment variables allows for further flexibility in organization and extensibility with the Base Environment and Sub Environments. In this scenario, a Collection is a collection of API routes for a specific App. For instance, I need a Collection to utilize a Sub Environment with specific variables for actual environments (Prod, Test, Dev). This is currently possible as you can select the environment once in a Collection. You might say this is exactly what I am asking, but there's a difference: this sets the environment, but there are Apps, a.k.a "Collection", specific configurations that are desired for different Apps, e.g. the App's name that feeds directly into the URL. Sure,…