Description
From PowerShell/PowerShellEditorServices#1214.
At startup there's no way to opt-in to loading PSReadLine and we get message like #2504.
At this point the prompt becomes largely useless.
The user workaround to this is to trust the Microsoft certificate, with which PSRL is signed. (This is distinct from the Windows-inbox certificate, which is the only one trusted by default).
A built-in workaround to this would allow us to load the PSRL module at startup in some way, either by intercepting the prompt and giving it the right response, or by otherwise unblocking the file in some way (Unblock-File does not achieve this).
A solution would be for us to consume PSRL not as a PowerShell module but as a .NET dependency, for example in NuGet.
/cc @daxian-dbw