Handle watermarked assets

Problem/Motivation

Now that we are able to retrieve streamed assets (#3451497), the module needs to also be able to handle configuration for watermarked asset formats. In other words, we need a way to configure which content types might have watermarked asset formats, and what those formats are, on a per-content-type basis.

Building on this, we need to provide getters that will allow code to easily find out, based on content type, and if a watermarked format is needed, which format to use in the code.

API changes

The ability, in OrangeDamConfigurationManager::getAssetFormat() to not only request the base asset format for a content type, but also the watermarked asset format for a content type.

The ability to test if a given format is a (valid/configured) watermarked asset format (in OrangeDamConfigurationManager::isWatermarkedAssetFormat()).

Data model changes

The config schema for orange_dam.settings.yml has been updated to allow for configuration of watermarked assets.