Users do not realize creating new content type includes a body field

Problem/Motivation

This was discovered 8-ish years ago in 🌱 [meta] Fix issues found during UMN Usability Testing 2015 Active but presumably still a concern. When a new content type is created a body field is "automatically" created for it, which a user might not expect.

Perhaps when creating a field there can be an option to create the body field with it, and that option can default to TRUE so there's no difference in existing behavior, but a user is now empowered to opt out of it.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Release notes snippet