Actionabilize errors from incorrect settings files (#1263)
Actionabilize errors from incorrect settings files (#1263)

* Annotatively research current state of exception handling surrounding settings file load invocation

* Throw a contextful terminating error if processing the argument of 'Invoke-ScriptAnalyzer -Settings' results in an exception

* Refine id and category of error for when processing value of `Invoke-ScriptAnalyzer -Settings` results in an exception

* Revert "Annotatively research current state of exception handling surrounding settings file load invocation"

This reverts commit 3bfd45ba6ccf0de5b3853228d85130f18e342071.

* Do not attempt id and category inference for the error to throw when processing the argument of `Invoke-ScriptAnalyzer -Settings` results in an exception

* Remove `using System.IO`

* Revert "Remove `using System.IO`"

This reverts commit 88ab1ec889f69deb0fe2e569ceaf2f0b65595327.

`using System.IO` is required in Engine\Settings.cs after all. The main
use is for pre-existing unqualified references to the type
InvalidDataException.

* Remove unused using after refactoring. Use more descriptive variable name and make error record arguments consistent with usage in other parts of the solution.

PowerShell/PSScriptAnalyzer