Include solution action in PowerPlatformDeployPackage task log

[filcole]

When using the Package Deployer task in the Azure DevOps Power Platform Build Tools the full package deployer logs are only output at the end of a run as a pipeline artifact and a less verbose log is written to the devops logs whilst the task is running.

It would be great if the package deployer decision on whether to install, skip, update or upgrade a solution was shown in the devops logs.

e.g. in the anonymised log snippet below we can only infer via the timings that something happened for ''ACME Solution Sol A' (but was it an upgrade or install?).

2022-09-28T01:02:43.1480136Z ##[section]Starting: PowerPlatformDeployPackage
2022-09-28T01:02:43.1598070Z ==============================================================================
2022-09-28T01:02:43.1598389Z Task         : Power Platform Deploy Package
2022-09-28T01:02:43.1598687Z Description  : Power Platform Deploy Package. Requires Windows build agent
2022-09-28T01:02:43.1598922Z Version      : 2.0.7
2022-09-28T01:02:43.1599083Z Author       : Microsoft
2022-09-28T01:02:43.1599324Z Help         : [More Info](https://aka.ms/buildtoolsdoc)
2022-09-28T01:02:43.1599614Z ==============================================================================
2022-09-28T01:02:43.4084115Z Discovered environment url from explicit input parameter 'Environment': $(BuildTools.EnvironmentUrl)
2022-09-28T01:02:43.4090169Z Discovered Azure DevOps variable expression that needs resolving: $(BuildTools.EnvironmentUrl) -> BuildTools.EnvironmentUrl
[ ... snip ... ]
2022-09-28T01:02:58.1122909Z [ '36. Dependency Found : Dependency on solution msdynce_CustomerServiceHubPatch found on target environment' ]
2022-09-28T01:02:58.1123520Z [ '37. Dependency Found : Dependency on solution BaseCustomControlsCore found on target environment' ]
2022-09-28T01:02:58.1124095Z [ '38. Dependency Found : Dependency on solution CustomControlsCore found on target environment' ]
2022-09-28T01:02:58.1124702Z [ '39. Dependency Found : Dependency on solution msdynce_ProductManagementPatch found on target environment' ]
2022-09-28T01:02:58.1272335Z [ 'Reading the solutions. Please wait.' ]
2022-09-28T01:02:58.1273473Z [ '1. Dependency Found : Dependency on solution msdynce_LeadManagement found on target environment' ]
2022-09-28T01:02:58.1274108Z [ '2. Dependency Found : Dependency on solution FieldService found on target environment' ]
2022-09-28T01:02:58.1274573Z [ 'Found 14 solutions.' ]
2022-09-28T01:02:58.1278156Z [ 'Found the detailed data to import.' ]
2022-09-28T01:02:58.1278733Z [ 'Checking configuration for Finance and Operations application' ]
2022-09-28T01:02:58.1324942Z [ 'Checking configuration for Finance and Operations application' ]
2022-09-28T01:02:58.1343869Z [ '' ]
2022-09-28T01:02:58.3226770Z [ 'Importing solutions' ]
2022-09-28T01:02:58.5405255Z [ 'Beginning load of solution ACME Solution Controls, version: 1.0.0.4.' ]
2022-09-28T01:02:58.8450329Z [ 'Beginning load of solution ACME Solution Controls OSS, version: 1.0.0.2.' ]
2022-09-28T01:02:59.1263568Z [ 'Beginning load of solution ACME Solution Legacy Controls, version: 1.0.0.1.' ]
2022-09-28T01:02:59.4232629Z [ 'Beginning load of solution ACME Solution Images, version: 1.0.0.4.' ]
2022-09-28T01:02:59.7201881Z [ 'Beginning load of solution ACME Solution Core, version: 1.0.0.45.' ]
2022-09-28T01:03:00.0169852Z [ 'Beginning load of solution ACME Solution Readings, version: 1.0.0.3.' ]
2022-09-28T01:03:00.2983185Z [ 'Beginning load of solution ACME Solution Sol A, version: 1.0.0.49.' ]
2022-09-28T03:01:10.4570930Z [ 'Beginning load of solution ACME Solution Sol B, version: 1.0.0.8.' ]
2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol C, version: 1.0.0.15.' ]
2022-09-28T03:01:11.0414198Z [ 'Beginning load of solution ACME Solution Sol D, version: 1.0.0.4.' ]
2022-09-28T03:01:11.3409011Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.12.' ]
2022-09-28T03:01:11.6343037Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.1.18.' ]
2022-09-28T03:01:11.9270838Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.23.' ]
2022-09-28T03:01:12.2240285Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.0.15.' ]
2022-09-28T03:01:12.5214303Z [ 'All solutions import complete.' ]
2022-09-28T03:01:12.5223218Z [ 'Installing Finance and Operations application' ]
2022-09-28T03:01:12.7330090Z [ 'Installation completed for Finance and Operations application' ]
2022-09-28T03:01:12.7336960Z [ 'Installing Finance and Operations application' ]
[ ... snip ... ]

i.e. It would be good if the snipped from the PD logs, e.g.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol C, version: 1.0.0.15.' ]  existing version [1.0.0.15]. Solution skipped.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol D, version: 1.0.0.15.' ]  existing version [1.0.0.14]. Upgrading solution.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol E, version: 1.0.0.15.' ]  existing version [1.0.0.14]. Upgrading solution.

2022-09-28T03:01:10.7536829Z [ 'Beginning load of solution ACME Solution Sol F, version: 1.0.0.15.' ]  solution not installed.  Installing solution.

[davidjenni]

@filcole the proposed improvement makes sense but is not trivial to implement: pac CLI is using a common PackageDeployer library that is also leveraged in other hosts, like PDS/TPS.
Not all the state changes are easily accessible from the pac CLI host (short of parsing the log/text stream the CLI already captures, but that tends to be brittle over time)