Create implementation plan for updated Editor.js

[greensomes]

Document the plan to implement the new version of Editor.js in Dev, including a rollback plan for the database in the event that CircleCi needs to be run to push content to prod.

[greensomes]

• Take a backup of the database
• Merge issue branch into dev to initiate the CMS build. This requires the config.yml update to automate the building of Directus extensions when specific folders in the code base have been modified.
• Manually run the Node application to process and transform Editor.js JSON data in the card_blocks and content_blocks collections.
• Perform testing in the CMS.
• Perform testing in the application frontend.
• To revert the changes, restore the database with the backup taken before the migration started.
• A rollback of the CMS code should not be necessary prior to running CircleCi to migrate the dev database to prod.

[greensomes]

Here's how to take the database backup:

cf target -s dev; cg-manage-rds export -o "-F c" -f ./dev-onrr-psql-backup.pg dev-onrr-psql

And to restore from the backup:

cf target -s dev; cg-manage-rds import -o "-F c" -f ./dev-onrr-psql-backup.pg dev-onrr-psql

[greensomes]

See issue #3195 for previous uses of cg-manage-rds.