Refactor for Power Platform environments

[appieschot]

We currently have two implementations that list the Power Platform environments m365 pa environment get and m365 flow environment get. This is mainly because of legacy reasons as a while back those environments where slightly independent of each other. To achieve better parity with the Power Platform we should refactor this to a single command.

We should introduce a new group, the pp (Power Platform) group and could have the m365 pp environment get commands grouped under there. That would require just a single implementation. In addition to that we could still keep the m365 pa environment and m365 flow environment commands as alias so that if you are less experienced with the Power Platform structure you still can use the commands to work with environment settings.

By doing so we free ourselves up to also implement commands like environment add and environment backup.

@pnp/cli-for-microsoft-365-maintainers please chime in, if we agree I can draft up the specs.

[waldekmastykarz]

Centralizing implementation and avoiding duplication would help us cut the amount of code and simplify maintenance so I'm all for it. I'm not sure about the generic pp namespace as I suspect folks tend to think in specific products like Power Apps or Power Automate rather than generic suites like Power Platform, but if we can find confirmation that it would be clear to our users, I'd be all for it. Even if we decide against using the pp namespace, we could still dedupe the commands, so one doesn't exclude the other ;)

[appieschot]

@Laskewitz you are a Power Platform guru ;-) Would you mind sharing what you hear in the community?

[Laskewitz]

@waldekmastykarz @appieschot I see more and more assets (PAC CLI/PowerShell etc) slowly move away from specific commands (power apps/power automate/flow) because of the same reason, so it's probably not weird (I would prefer it actually) to go for pp here.