Multiple ways to set a recordId is causing issues

The addition of recordId to the constructor signature for Pipeline and DataManager has created issues where some situations set the recordId and some don't. This is just confusing for users too so the best solution is to remove that from the signature and only allow setting in the `settings` object