DIGITAL-61: export default content type for glossary

[cathybaptista]

Jira ticket

DIGITAL-61

##Relates to

Digital-43
Digital-60

Purpose

Acceptance Criteria:

A few sample entities are exported via default content.

QA/Testing instructions

1. Pull branch

2. Drush CIM

3. lando rebuild && lando si

4. Taxonomy module should be enabled.

5. Edit one of the guide pieces of content.

6. Select "HCD Glossary" under the HCD Glossary field.

7. Make sure the "Glossary" button appears.

Checklist for the Developer

• A link to the JIRA ticket has been included above.
• No merge conflicts exist with the target branch.
• Automated tests have passed on this PR.
• A reviewer has been designated.
• Deployment and testing steps have been documented above, if applicable.

Checklist for the Peer Reviewers

• The file changes are relevant to the task objective.
• Code is readable and includes appropriate commenting.
• Code standards and best practices are followed.
• QA/Test steps were successfully completed, if applicable.
• Applicable logs are free of errors.

[cathybaptista]

@mattsqd let me know if you didn't want 61 to be based on 60 and 60 on 43. Just trying to save work, but may have just made some instead.

[omerida]

Guide content updated as advertised.