PL-400: Microsoft Power Platform DeveloperDemo

For issue 1, the fact that Solution checker completes for one solution but not another rules out a disabled Power Apps checker application user: if that service account were disabled, no solution would run at all. A run that fails only for a specific solution points to invalid content inside that solution, such as a canvas app with errors that the checker cannot process. For issue 2, a runtime error thrown on a specific line of a JavaScript web resource is the signature of strict mode ("use strict"): strict mode converts otherwise-silent mistakes (assigning to an undeclared variable, duplicate parameters, etc.) into thrown errors at that line, which the web-use-strict-mode rule concerns. web-avoid-modals (blocking alert/confirm dialogs), web-avoid-eval and web-remove-debug-script describe different problems and would not surface as a line-specific execution error.