Adding UserInput or UserApp Exceptions

[NavneetThekkumpat]

User input errors are not handled gracefully. This is keeping in mind the behavior with the consumption of test engine in PAC CLI. Few cases below handled. Also updated a case to handle as User app exception. This will help us isolate this type and localize in PAC CLI side. Categorizing mainly these specific errors into

1. UserInputExceptionInvalidFilePath.
2. UserInputExceptionLoginCredential.
3. UserInputExceptionTestConfig.
4. UserInputExceptionYAMLFormat
5. UserAppException

Validation

• Unittesting
• Manual Testing

Console Output Scenarios

• 
• 
• 
• 

With this PAC test run will handle such scenarios gracefully (second run has this fix).

Checklist

• [x] The code change is covered by unit tests. I have added tests that prove my fix is effective or that my feature works
• [x] I have performed end-to-end test locally.
• [x] New and existing unit tests pass locally with my changes
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] My changes generate no new warnings
• [x] I used clear names for everything
• [x] I have performed a self-review of my own code

[landonmsft]

Looks good, besides flip-flopped names for two 'cs' files, UserAppException/UserInputException

[github-actions[bot]]

Package	Line Rate	Branch Rate	Complexity	Health
Microsoft.PowerApps.TestEngine	91%	87%	974	✔
Summary	91% (2536 / 2781)	87% (593 / 678)	974	✔

Minimum allowed line rate is 85%