Minor fixes for PegaRULESLongRW data source

• #418 PegaRULESLongRW data source to actually take/use password and connection properties.
  • This data source previously didn't take any password - assuming a secretsmanager jdbc driver approach - and hardcoded the connection properties. Now it uses same connection info as main PegaRULES data source, and appends the hardcoded (timeout) properties to the passed ones.
  • This data source is not currently in use by Client Managed Cloud environments, confirmed by the fact that it did not take any password. Without CloudK specific handling, it was not a valid data source. Intended behavior was for it to use same JDBC connection URL as PegaRULES datasource, so now it can reuse the main PegaRULES jdbc url by setting SET_RW env var, and not JDBC_RW_URL