Flows: physical to logical datatype rippler should use a dedicated provenance

[davidwatkins73]

Description

Currently it is hard to tell at a glance if the data type on a logical was rippled up from a physical. This is because the PhysicalSpecDecoratorDao::rippleDataTypesToLogicalFlows method has the hard coded values waltz for provenance and admin for the user id.

Suggest we change the to be more explicit (data-type-rippler / automated-job) ?

Resourcing

We intend to contribute this feature