Simplify getting metadata for Schema, Open Graph, Twitter Card, and Search Meta

[JSn1nj4]

Thinking:

• Contracts
• DTOs
• Blade components
• DTOs should have appropriate defaults—in theory, a new DTO should not error
• DTOs may have a from method that accepts an object that can supply appropriate fields
• Contract implementers may have to<MetaType>DTO methods
• Contract implementers may have <MetaType>Fields field maps
• Blade components should not error on a zero-length field, just decide if a meta tag should be created

Schema

• SchemaDotOrgContract
• SchemaDotOrgDTO
• SchemaDotOrg (component)

Open Graph

• OpenGraphContract
• OpenGraphDTO
• OpenGraph (component)

Twitter Card

Gonna start using X instead of Twitter on new stuff.

• XMetaContract
• XMetaDTO
• XMeta (component)

Search Meta

This stuff is a maybe. Title and meta description are already used in a few places.

• SearchMetaContract
• SearchMetaDTO
• SearchMeta (component)

[JSn1nj4]

For X, should have Summary Card fallback using avatar instead of large image if no large image available. That would be a cool fallback.
https://developer.twitter.com/en/docs/twitter-for-websites/cards/overview/summary