non-working SWE Opportunity component updates

[katcui]

Changes made to .env and SWE Opportunities component so that page refers to the SimplifyJobs repo and updates accordingly. The current code does not work and some error occurs during decodeREADME function resulting in a fetch error.

• Added the new API to .env to access SimplifyJobs repo, and set as new readMeURL under SWEOpportunitiesComponent.
• Defined 2 separate regex's: one matches lines containing company name (and link), other matches lines where company field is an arrow
• Rewrote the while function to consider both cases and act accordingly: if matches first regex, 7 capture groups (because company field has text and link). If it matches second regex, 6 capture groups (because company field is just a symbol)
• Redesigned the table to display information corresponding to the SimplifyJobs repo

Changes should technically make it so that the lines of 'content' are iterated through and matched to either the first or second regex, and have the values updated accordingly and added into jobList. They should display almost the same was as it does in the repo, where the company name is either the name with the link or an arrow. Since I decided to keep the arrow as the title, because I couldn't figure out a way to fetch the last company name in content and replace it as such, there will be issues with the job filtering.

Certain things I think may be causing the error because I may not understand:

• how does the while loop iterate through the lines of 'content' and how that is affected by the if statement
• whether or not the redeclaraction of match in the while loop and if statement effects what is being read
• whether or not the regex's are completely correct in capturing the substrings
• storing 'company' and 'application' as objects and retrieving their data in the table design
• 'company' object's url when matched to the second regex (company name is an arrow) is null, but I didn't include the link in the table in case this caused problems but it could also just be a problem

Possible changes I could include:

• rewriting the regex's to ignore the link in the company name (same as application link)
• separating data in objects 'company' and 'application' so that there's less complexity to designing the table

[vercel]

Someone is attempting to deploy a commit to a Personal Account owned by @ethanpaneraa on Vercel.

@ethanpaneraa first needs to authorize it.