Initial version of the new HTTPS RadioPlayer upload.
Add in uploading to S3 buckets in addition to the FTP / HTTPS services.
Point the HTTPS uploader at the new Nitro publisher.
Alter crid generation to ensure nitro and bbc uris are changed to the same crid on output.
Ensure that new Nitro image urls are parsed and dimensions converted in a similar fashion to the dynamite uris.
Allow configuration of which services to upload for, for the HTTPS RadioPlayer uploader.
Tweak behaviour of enabling flags for RP Upload, so that each remote service upload can be enabled separately, and the s3
upload can be turned on and off independently of both.
Ensure that module still adds tasks if there are no ftp credentials, and ensure the health controller
knows about the non-ftp services.
Trust all SSL certs, because Radioplayer dev certs aren't set up properly.
Replace use of curie to generate urls with the canonical uri.
Ensure the Caching File upload store knows about both https and ftp services when created.
Selection of fixes.
 - Ensure clip outputter uses canonical uri rather than curie.
 - file controller takes publisher, so files are generated per publisher rather than just for a single publisher
Ensure that the s3 serviceId is added to the list of remote service if s3 upload
is enabled.
Reverse map of publisher to string to be map of string to publisher.
Separate out s3 remote service, and only add it to the caching store, not the health probes or the
main rp controller.
And again...
Return all successful uploads from fileUploadStore, then filter for those with unknown remote
results.
Check the transaction id not the message.
Remove status check in remote processing checker
Ensure nitro urls are coped with when creating the audio source urls