Cache scraper results

[chimon2000]

Is your feature request related to a problem? Please describe.
Currently, the scraper results are stored in a JSON file. This will not scale well, so we should choose a better caching solution.

Describe the solution you'd like
Ideally, we would store the results in Firestore. This gets rid of the need to maintain and extend an API.

A secondary option is caching the results in an appropriate caching solution (either Memcache or Redis)

Results that are more than 30 days in the past should be expired.

Describe alternatives you've considered
n/a

Additional context
n/a

[AndrewNatoli]

Suggestion: Since we're currently doing a full pull when we run the spiders we might as well wipe and replace the full cache on run instead of worrying on managing the TTL of data for now

[chimon2000]

I actually decided that maybe we are overthinking this. Let's just store the results in Firestore, scrap the idea for an API, and have the app pull directly from the Firestore.

[chimon2000]

Here is the current structure of Community events

community-events/web/src/types/custom.d.ts

Lines 1 to 16 in ecdc1d6

	type CommunityEvent = {
	id: number
	title: string
	description: string
	date: string
	tags: string[]
	locations: EventLocation[]
	learnMoreUrl: string
	time: string
	}
	type EventLocation = {
	name: string
	locationRoom: string
	locationUrl: string
	}