Quicksilver has two assembly bindings to EPiServer.Cms.UI.AspNetIdentity

Description

Steps to reproduce

1. Use Quicksilver (newer than version 11.5.0.) It works here: https://github.com/episerver/Quicksilver/tree/2bac9c737a03369a0c4f59610c899d401047925a)
2. Upgrade the EPiServer.Cms.UI.AspNetIdentity package.

Expected: To get a new version.

Actual: Error

The property 'oldVersion' cannot be found on this object. Verify that the property exists and can be set.
At C:\Episerver\QS 11.6.0\packages\EPiServer.CMS.UI.AspNetIdentity.11.2.1-pre-001078\tools\Update-AssemblyBinding.psm1:103 char:5
+     $assemblyConfig.bindingRedirect.oldVersion = "0.0.0.0-" + $assemblyName.Vers ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException
 
The property 'newVersion' cannot be found on this object. Verify that the property exists and can be set.
At C:\Episerver\QS 11.6.0\packages\EPiServer.CMS.UI.AspNetIdentity.11.2.1-pre-001078\tools\Update-AssemblyBinding.psm1:104 char:5
+     $assemblyConfig.bindingRedirect.newVersion = $assemblyName.Version.ToString( ...
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : PropertyAssignmentException

The error occurs because there are two assembly bindings of the same assembly, and the powershell scripts can't handle that.