Apply Default Values to the CoreData items added in 117

[chipsnyder]

Fixes a migration issue that was a result of changes made when adding some values to the 117 Data Model.

To test:

1. Install a previous build such as one from trunk
2. Navigate to the page creation screen where you can pick starter content
   • This will populate entities that will be migrated in the next step
3. Install a build from this branch
4. Expect the Migration to be successful
5. Navigate to the page creation screen where you can pick starter content
6. Expect to not have any issues loading that page

PR submission checklist:

• I have considered adding unit tests where possible.
• I have considered adding accessibility improvements for my changes.
• I have considered if this change warrants user-facing release notes and have added them to RELEASE-NOTES.txt if necessary.

[peril-wordpress-mobile]

You can trigger an installable build for these changes by visiting CircleCI here.

[peril-wordpress-mobile]

	Warnings
⚠️	Core Data: Do not edit an existing Core Data model in a release branch unless it hasn't been released to testers yet. Instead create a new model version and merge back to develop soon.
⚠️	PR has more than 500 lines of code changing. Consider splitting into smaller PRs if possible.

Generated by 🚫 dangerJS

[peril-wordpress-mobile]

You can trigger optional UI/connected tests for these changes by visiting CircleCI here.

[mkevins]

I tested this by the steps described, and it's working without a migration failure now. Thank you for tackling this with the version bump Chip!