Make use of profiles for compose up subset / compose tasks

[bwateratmsft]

https://docs.docker.com/compose/profiles/

[bwateratmsft]

Services and profiles are not compatible; i.e. if you specify services then profiles will be ignored. So, we'd need the task to allow either services or profiles, but not both. I'm not sure yet of a good way to integrate profiles with the subset up command.

[bwateratmsft]

For tasks this is easy; just have "profiles" as an alternative to "services" in the args. For the command it's more complicated. If we can inspect the compose doc to find profiles, it may make sense to ask the user to pick either individual services or profiles.

[bwateratmsft]

Upstream, these changes would be nice--make it far easier to determine profiles: docker/compose#8211 / docker-archive/compose-cli#1476

Update: the upstream changes have been implemented! Woohoo!

[bwateratmsft]

I'm stuck on this at the moment. The docker-compose config --services command only will list services that do not have profiles associated. As a result, if a compose project has profiles, and the user still wants to select by service...well, the UX is terrible, they won't see what they want.

I really, really, really want to avoid parsing the document, especially considering how much compose is in flux right now.

[bwateratmsft]

I've pushed what I have to the bmw/composeProfiles branch. I think it's more or less working end-to-end, and would have a good enough UX if it weren't for the above unlisted services issue.