Further support manual upgrade use case providing segregated scripts for CM.

Currently in order to apply the database changes required to update/upgrade Alfresco one must run the upgrade in a test environment and then retrieve the DDL generated. Even with db.schema.update=false some level of SQL manipulation is happening within the Alfresco repo
code to apply additional changes to the Alfresco database. This proves challenging for organizations with CM policys dictating that they must separate these tasks requiring elevated permissions.

Customer is requesting that the DDL be provided for upgrade paths as well as a means to execute any additional database changes required for the upgrade via a DBA centric manner. I.e. leverage something like PL/SQL, stored proc, etc rather than having to execute java code to perform the
changes.