Outputing Exceptions is not honoring no_color and leaves red color on

[simonsabin]

Prerequisites

• Write a descriptive title.
• Make sure you are able to repro it on the latest released version
• Search the existing issues.
• Refer to the FAQ.
• Refer to Differences between Windows PowerShell 5.1 and PowerShell.

Steps to reproduce

either run in powershell

$env:no_color="on";pwsh  -noninteractive -Command "$errorview='NormalView';throw 'an Error'"

or run this in a command prompt

set no_color=on&pwsh  -noninteractive -Command "$errorview='NormalView';throw 'an Error'"

Expected behavior

Error is output but in the consoles forecolor

Actual behavior

Error is output in red AND the console prompt stays in red

Error details

No response

Environment data

Name                           Value
----                           -----
PSVersion                      7.2.6
PSEdition                      Core
GitCommitId                    7.2.6
OS                             Microsoft Windows 10.0.22000
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           1.1.0.1
WSManStackVersion              3.0

Visuals

[simonsabin]

Related to #16643 in trying to get powershell to not output ANY ansi escape characters.

[jhoneill]

The red in error isn't done with ANSI , see below for the issue and what's being done.
#17886 (comment)

Hopefully when it is done with ANSI then it will honour no_color etc. (AIUI no color only applies to ansi, not Write-Host -Foregound ... and error is currently doing the equivalent of that.)

[simonsabin]

Duplicate of #17886

[simonsabin]

The red in error isn't done with ANSI , see below for the issue and what's being done.

Looking at this, not sure this fixes exceptions occuring when pwsh runs such as incorrect script passed to -Command, given PsStyle won't have been set.

[daxian-dbw]

This is a duplicate of #17885, which was fixed.