Namespaced blob providers

It's now possible to request a blob provider where there hasn't been any explicit configuration for it, using BlobManager.getBlobProviderWithNamespace(id) . If there is no blob provider configured for this id, then the default one will be used, although using a  namespace  based on the id to avoid collisions. For the filesystem-based blob provider, if the default  is stored in .../data/binaries/... then a namespaced provider for myid will be stored in .../data/binaries_myid/... For the S3 blob provider, the binaries of a namespaced provider myid  will be stored in a S3 "subfolder" named myid/ under the storage for default . Azure works similarly. Also, a blob provider whose name starts with transient will automatically be flagged as transient (see  NXP-24421 ) to avoid manual configuration.