[META] Track 7: Create "Events" recipe

I'm not sure what format is helpful for feedback here, but here are some thoughts, based on my own experience working with dates in Drupal, as well as looking at event handling in other calendar software from companies like Google, Apple, and Microsoft.

For the content entry, common widget patterns include:

• Inputting an event as a time range, with a concept of duration, so that setting the start time automatically sets the end, based on the duration
• Default time is the next hour (on the hour, no minutes or seconds)
• No seconds inputs
• An "all day" checkbox
• Ability to handle timezones (could be hidden by default)
• Ability to set an event as recurring (could be hidden or disabled by default)

For formatting the event dates and times, the solution should deduplicate parts of the date that are common to the start and end. For example, instead of output such as:
8:00am June 15, 2024 - 10:00am June 15, 2024

...it should create output like:
8:00 - 10:00am June 15, 2024

...or for date ranges:
June 15 - 17, 2024
June 30 - July 2, 2024

I would suggest that the recipe should also create an event listings page, including tabs for upcoming and past events. Perhaps it could also provide a block listing upcoming events, and automatically place it in the sidebar on the home page.

Many sites also want a calendar display, though it may not be necessary as part of the standard recipe. Having a calendar display as an available add-on would add value to the events recipe, however.

Looking at a comparison of WordPress event plugins suggest some other possible features, including:

• Registration (potentially including paid)
• Booking management, including approval and rejections
• Integration with calendar apps
• The ability to display the event location in a map
• Notifications/reminders before an event's start

I would suggest that these are more advanced features that don't need to be included in the standard recipe, but having them available within the broader ecosystem would be valuable.

Event content type should follow Google specified schemas as defined at:
https://developers.google.com/search/docs/appearance/structured-data/event

The event experience on Google makes it easier for people to discover and attend events through Google Search results and other Google products, like Google Maps.

In order to make it easy for a site builder to quickly apply a rich set of event management capabilities, it would be ideal if all available capabilities could be presented during the initial application of the recipes. As such, tagging as related a couple of issues around optional config and getting user input.