Bump Microsoft.Identity.Client from 3.0.8 to 4.22.0 for Azure.Identity compatibility

Incompatibility notice. Pay attention, please!

Assets are decoupled

Starting from this version, the Platform does not contain assets-related functionality anymore. It was decoupled into three modules separately out of the platform:

All three modules are included in the "commerce" bundle and installing with every new platform installation.
If you are upgrading the platform in your assets supporting system, please install all three modules, otherwise assets functionality becomes unavailable.

"Commerce" bundle modules compatibility

All the modules versions lower than enlisted below are not compatible with this and future versions of the Platform.

Converting your custom module to use newly created VirtoCommerce.Assets module

If your custom module uses assets functionality from the Platform you need to make several changes to your module.

1. Add a dependency into the module.manifest to the latest available VirtoCommerce.Assets module;
2. Add nuget package reference in related projects to the latest available VirtoCommerce.AssetsModule.Core package;
3. Remove using of VirtoCommerce.Platform.Core.Assets namespace from your code and add VirtoCommerce.AssetsModule.Core.Assets instead;
4. If your module extends Admin UI, change assets related endpoint uris URIs: 'api/platform/assets?XXXXXXX' -> ''api/assets?XXXXXXX';
5. If your module extends Admin UI and uses angular templates from the assets modules, change templates URIs similar way: '$(Platform)/Scripts/app/assets/blades/XXXXXXX' -> 'Modules/$(VirtoCommerce.Assets)/Scripts/blades/XXXXXXX'