Version 3 to Version 4 upgrade path and utility

[rosalindlopez]

Critical Changes

Tweaks to sfdx-project.json, cumulusci.yml, and readme.md files to add additional instructions and better enable work with CumulusCI in scratch orgs.

Changes

Added an unpackaged/labs-upgrade folder and a new CCI task for installing this into orgs. The labs-upgrade contains a screen flow that kicks of an apex class. The class copies Unsubscribe records from the old unnamespaced object into the new packaged object. It also copies the 18 digit Id of the old object to the new object for auditing purposes.

Also added two metaDeploy plans: one for a basic install and one to install the labs upgrade package folder.

Issues Closed

#89

[rosalindlopez]

A note that the deployment of the labs_upgrade_package task should be built into MetaDeploy plan (either part of the basic install or as an optional additional plan) once this is published to the Commons MetaDeploy site.

EDIT: I added draft metadeploy plans to the cumulusci file that should handle the base install and an optional plan for adding the upgrade utility if the org qualifies. however I wasn't able to test these fully so someone else should before they are widely distributed.

[salgsstyrke]

@rosalindlopez this is AMAZING!!! Thank you!! Can you clarify for me how a non-developer will install this? At the sprint next week I'd love for some folks to prepare instructions. Do you have that info in the read me files? cc @DKeatonDC

[rosalindlopez]

@salgsstyrke installing this does require using CumulusCI, but the custom task should enable non-developers to do it as long as they can set up CCI on their computer.

Now that we've gotten the automatic generation of beta packages working, the following CCI commands should install the labs/v3 version, then the latest commons/v4 package, and then the upgrade utility:

1. cci task run install_v3
2. cci task run install_managed_beta
3. cci task run labs_upgrade_package

[salgsstyrke]

@rosalindlopez what about... to really dumb it down... people who have both packages already installed they can paste in the apex code and make the flow to launch it?

[rosalindlopez]

@salgsstyrke They could paste in the code and then either build the flow or launch it as anonymous apex. It does depend on a custom field Migrated_record_id__c on the unsubscribe record so they would need to create that manually as well.

[salgsstyrke]

Thank you! @rosalindlopez Most users of the app are not very technical. We could go ahead and add in that field to the main package so they wouldn't have to recreate it.