Add TicketTailor integration + EventList block

[janbaykara]

Allows importing data from TicketTailor.

Description

• Adds TicketTailorSource and connection boilerplate
• Adds new flags, tests, code and UI guard-rails for read-only data sources
• Adds an EventList block in Puck to display event data. You can select a data source and filter out certain events.
• One outstanding task is to add import webhook support. We need webhook logic for triggering imports when these webhooks come in, and we need UI to display the webhook URL to the user so they can enable it.

Motivation and Context

TicketTailor is used by the Climate Coalition to organise RSVPs for their training schedule and, alongside EventBrite, is one of the few big ticketing/events platforms.

Events are a common type of geographically mappable entities, given they generally a location and a time. But even if they are online, a public hub should route people to relevant events.

This PR makes it possible to advertise events from these third parties in curated, dynamic maps and timelines.

It also sets the scene for other read-only data sources like EventBrite, hosted CSVs, JSON APIs, SQL databases and much else.

How Can It Be Tested?

You can run the tests locally by adding TEST_TICKET_TAILOR_API_KEY to your .env.

Bitwarden login for https://tickettailor.com/ is [email protected] — you can find the API key in Box Office Settings > API

1. Connect TicketTailor as a CRM — you should have no options beyond the name
2. In the inspector, there should be no update options
3. Import data
4. Create a map and display some events there

How Will This Be Deployed?

N/A

Screenshots (if appropriate):

Types of changes

• New feature (non-breaking change which adds functionality)

[linear]

MAP-263 TicketTailor integration

[joaquimds]

suggestion: we should keep these default variables to squash console error logs, but restrict them based on the externalDataSourceType.

[janbaykara]

OK, I can revert these changes.

[janbaykara]

Fixed. Noticed a separate bug where postcode field doesn't get prefilled anymore by guesser.

[janbaykara]

I feel the URL and instruction should appear after connection. There are two instructions for sources that don't have automated webhooks:

1. The import URL and instruction
2. For sources that allow updates, the import URL and instruction

Could also be a follow-on PR.