PR Summary

Some terminals can turn the script:line into a hyperlink, so adding the line number right after the filename allows it to be clickable and takes you to the line of the error instead of just the file. This does make the line number information redundant, but is not a big issue. Since this is similar to what users already saw in NormalView, they should understand what that number represents.

However, if we are running in vscode, it also understands script:line:col making the link click to the location of the error so we add column information only for vscode terminal.

Get-ChildItem: /Users/steve/test/multierror.ps1:3
Line |
   3 | Get-Childitem -Path .\nothere
     | ^ Cannot find path '/Users/steve/repos/PowerShell/nothere' because it does not exist.

PR Context

Fix #10877

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).