As a reporting user, I want the ability to declare additional mondrian connection properties (like 'jdbcconnectionuid') on a mondrian connection

When run in standalone == false (inside BI server), PRD disregards the catalog properties that are present in datasources.xml. It builds a new connection string with a small subset of those properties (in PentahoCubeProvider).

This should be changed so that all properties in the catalog string are used to build the Mondrian Connection. This is relevant so that PRD can use the jdbcconnectionuid property newly introduced to Mondrian and, subsequently, share the Mondrian cache with the other platform components.

We propose that the PentahoCubeProvider class/mechanism should be replaced with a PentahoCatalogStringProvider that will create a catalog string with all the properties in datasources.xml