Verbose output produces base64 encoded text

Prerequisites

[X] Write a descriptive title.
[X] Make sure you are able to repro it on the latest version
[X] Search the existing issues.

Steps to reproduce

Specifying -Verbose on Out-ConsoleGridView produces base64-encoded strings like:

VERBOSE: TW9kZSRfLiJNb2RlV2l0aG91dEhhcmRMaW5rIg==
VERBOSE: TGFzdFdyaXRlVGltZSRfLiJMYXN0V3JpdGVUaW1lU3RyaW5nIg==
VERBOSE: TGVuZ3RoJF8uIkxlbmd0aFN0cmluZyI=
VERBOSE: TmFtZSRfLiJOYW1lU3RyaW5nIg==

Culprit TypeGetter.cs#LL172C1

Decoding these produces:

'TW9kZSRfLiJNb2RlV2l0aG91dEhhcmRMaW5rIg==', 'TGFzdFdyaXRlVGltZSRfLiJMYXN0V3JpdGVUaW1lU3RyaW5nIg==', 'TmFtZSRfLiJOYW1lU3RyaW5nIg==' | ForEach-Object { [System.Text.Encoding]::UTF8.GetString([System.Convert]::FromBase64String($_)) }
$ Mode$_."ModeWithoutHardLink"
$ LastWriteTime$_."LastWriteTimeString"
$ Name$_."NameString"

Expected behavior

Verbose output should help the user track the behaviour of the cmdlet and diagnose any potential problems.

Actual behavior

The user must decode the verbose output.

Error details

No response

Environment data

GitCommitId

PSRemotingProtocolVersion

PSVersion

Platform

SerializationVersion

PSEdition

WSManStackVersion

PSCompatibleVersions

7.3.4

2.3

7.3.4

Win32NT

1.1.0.1

Core

Microsoft Windows 10.0.19044

3.0

Major	Minor	Build	Revision	MajorRevision	MinorRevision
1	0	-1	-1	-1	-1
2	0	-1	-1	-1	-1
3	0	-1	-1	-1	-1
4	0	-1	-1	-1	-1
5	0	-1	-1	-1	-1
5	1	10032	0	0	0
6	0	0	-1	-1	-1
6	1	0	-1	-1	-1
6	2	0	-1	-1	-1
7	0	0	-1	-1	-1
7	1	0	-1	-1	-1
7	2	0	-1	-1	-1
7	3	4	-1	-1	-1

Version

0.7.2

Visuals