Support for data URLs for Creating CMS BLOBs

CoreMedia's Unified API allows to set the value of a BLOB property via a URL. BlobService.fromURL(String url) creates a BLOB to be fetched from the given URL. Besides the usual http(s) and file URL protocols, classpath and s3 URLs are supported. Now, also data URLs are supported, which are very useful especially for small BLOBs and plain text BLOBs. Since data URLs directly contain their MIME type and binary data, it does not make a semantic difference whether you use BlobService.fromURL() (data is fetched from the URL immediately), BlobService.fromURLReference() (data is fetched by the server), or BlobService.fromPersistentURLReference() (data is fetched on every usage, see JavaDoc for details).

(CMS-23318)

Studio is showing less commerce validation issues

Studio search can display commerce related validation issues, e.g if an augmented category cannot be found in the catalog. In the past, however, the studio showed a lot of errors if the commerce system was temporarily not available. Practically each commerce related content item (e.g. augmented categories, products, product teasers, product lists) appeared in the list as "invalid commerce id" issues. Now connectivity issues of the commerce adapter with the commerce system are recognized and no content issues are created. This feature requires a commerce adapter with a base adapter of at least version 2.2.x, because it propagates the gRPC response status UNAVAILABLE in case of connectivity issues with the commerce system.

(CMS-23038)