Update ConciseView to use TargetObject if applicable

[SteveL-MSFT]

PR Summary

If the ErrorRecord contains a TargetObject, try to use that instead of InvocationInfo where it's not as useful to the user.

Before:

PS> 1 + 1 | should -be 3
InvalidResult: /Users/steve/.local/share/powershell/Modules/Pester/4.4.0/Functions/Assertions/Should.ps1
Line |
 206 |         throw ( New-ShouldErrorRecord -Message $testResult.FailureMessage -File $file -Line $lineNumber -LineText $lineText )
     |         ^ Expected 3, but got 2.

After:

PS> 1 + 1 | should -be 3
InvalidResult:
Line |
   1 | 1 + 1 | should -be 3
     | ^ Expected 3, but got 2.

PR Context

PR Checklist

• PR has a meaningful title
  • Use the present tense and imperative mood when describing your changes
• Summarized changes
• Make sure all .h, .cpp, .cs, .ps1 and .psm1 files have the correct copyright header
• This PR is ready to merge and is not Work in Progress.
  • If the PR is work in progress, please add the prefix WIP: or [ WIP ] to the beginning of the title (the WIP bot will keep its status check at Pending while the prefix is present) and remove the prefix when the PR is ready.
• Breaking changes
  • None
  • OR
  • Experimental feature(s) needed
    • Experimental feature name(s):
• User-facing changes
  • Not Applicable
  • OR
  • Documentation needed
    • Issue filed:
• Testing - New and feature
  • N/A or can only be tested interactively
  • OR
  • Make sure you've added a new test if existing tests do not effectively test the code changed
• Tooling
  • I have considered the user experience from a tooling perspective and don't believe tooling will be impacted.
  • OR
  • I have considered the user experience from a tooling perspective and enumerated concerns in the summary. This may include:
    • Impact on PowerShell Editor Services which is used in the PowerShell extension for VSCode (which runs in a different PS Host).
    • Impact on Completions (both in the console and in editors) - one of PowerShell's most powerful features.
    • Impact on PSScriptAnalyzer (which provides linting & formatting in the editor extensions).
    • Impact on EditorSyntax (which provides syntax highlighting with in VSCode, GitHub, and many other editors).

[SteveL-MSFT]

@PoshChan please retry static

[PoshChan]

@SteveL-MSFT, successfully started retry of PowerShell-CI-static-analysis

[adityapatwardhan]

Signed off as maintainer. Would rely of area expert for code review.

[JamesWTruher]

I'm still uncomfortable with the obvious special handling for Pester

[adityapatwardhan]

@SteveL-MSFT Please resolve merge conflict

[ghost]

🎉v7.0.0-rc.1 has been released which incorporates this pull request.:tada:

Handy links:

• Release Notes