Part of #55238

In order to create different DataViews or DataForms for viewing, picking, or editing media, create dedicated fields for media/attachment properties.

These could include:

• alt_text
• caption
• description
• filename
• filesize
• media_dimensions
• mime_type
• media_thumnbail (display an image if available, fallback to displaying text of the filename?)
• attached_to
• date (read only)
• modified (read only)
• author (read only)

Use cases

• For the media modal (being explored in Try using DataViewsPicker in an updated media modal #71944)
• In a DataViews-powered media library
• In a media editor, and/or quick edit of media metadata

Some questions / considerations

• Where should the fields live? As discussed in Try using DataViewsPicker in an updated media modal #71944 (comment) if a post field like featured_image uses a media modal, and the media modal uses these media fields, then they likely shouldn't live in the same place as post fields (due to the risk of circular dependencies)
• Should there be a separate package specifically for these fields? I.e. media-fields or something like that, instead of the fields package?
• Related: should post fields (like featured_image) be more generic, and should there be a generic media_upload field that other fields can extend / re-use?