Commit to a strategy for rich / extended event descriptions

[brianfeister]

Our primary data being stored in vector DB (marqo) means that we don't want to allow users to dump event descriptions of infinite length into our DB. But we do want events to feel "special" which includes having the ability to show a bunch of images.

Short term, we could allow HTML in event descriptions, parse it, and users could host images on Google Drive or similar. It may even be preferable to have a "Google Drive Link / Integration" where users can connect their Google drive and insert images from there (via a "image picker" UI which then inserts the google-drive-hosted image with appropriate HTML into their event description)

Longer term, we could have a separate Dynamo table called "Extended Event Descriptions" and allow users to craft a separate extended description and then store that in Dynamo and lazy load it on Event Details pages. We should consider character count limit for base description such that it will run below the fold, allowing us to make that lazy load fetch call in a slow way that's off-screen, or maybe only "onScroll" when we know a user might be looking further into event details