Remove wiki-feed-parser, add logic to get feeds from supabase

[TueeNguyen]

Issue This PR Addresses

Fixes #2861
Waiting for #3373 to be merged, then update tests
Waiting for #3361 & #3359

Type of Change

• Bugfix: Change which fixes an issue
• New Feature: Change which adds functionality
• Documentation Update: Change which improves documentation
• UI: Change which improves UI

Description

• Rip out wiki-feed-parser.js => will need to update tests as well
• Add SUPABASE_URL & SERVICE_ROLE_KEY to parser in docker-compose.yml
• Add supabase client

Steps to test the PR

• pnpm install
• pnpm services:start parser
• Check the parser's container log, if feeds are being processed => it's good

How to run e2e test:

• pnpm services:start
• Stop the parser container
• pnpm jest:e2e parser

Checklist

• Quality: This PR builds and passes our npm test and works locally
• Tests: This PR includes thorough tests or an explanation of why it does not
• Screenshots: This PR includes screenshots or GIFs of the changes made or an explanation of why it does not (if applicable)
• Documentation: This PR includes updated/added documentation to user exposed functionality or configuration variables are added/changed or an explanation of why it does not(if applicable)

[gitpod-io]

[humphd]

@TueeNguyen you said you'd update this with details on what's blocking it, can you do that? I'd like to see this get in soon.

[TueeNguyen]

I'm tweaking the test, the PR should be up soon @humphd

[humphd]

I'm nervous about landing this until after 3.0-alpha happens, since we've never tested on Staging.

[TueeNguyen]

In our meeting today, we found out that this code could be removed

telescope/src/api/parser/src/parser.js

Lines 12 to 28 in d56306a

	const updateFeed = async (feedData) => {
	let currentFeed;
	// If we have an existing feed in the database for this URL, prefer that,
	// since it might have updated cache info (e.g., etag).
	const existingFeed = await Feed.byUrl(feedData.url);
	if (existingFeed) {
	// We have a version of this feed in the database already, prefer that
	currentFeed = existingFeed;
	} else {
	// First time we're seeing this feed, add it to the database
	const id = await Feed.create(feedData);
	currentFeed = await Feed.byId(id);
	}
	return currentFeed;
	};

It creates new Feed object and saves it to Redis, I think we still need this functionality. I can file an issue on this and open a new PR

[humphd]

See #3465 for similar code. I copied what you did, then fixed bugs in it.

[AmasiaNalbandian]

This is looking good when I run it!

[JiaHua-Zou]

Tested on my machine. Looks good!!