POC for #2379: GithubInfo Custom Hook to remove duplicate Github Info code

[HyperTHD]

Issue This PR Addresses

This PR addresses #2379

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

As part of #2379, We needed a way to reduce the amount of duplicate code used in our github info related components. This PR creates a new custom hook that deals with maintaining the amount of props we were passing into the github info components. As such, there's 0 props on all the components except for the users component since it needs the avatarSize prop to adjust for the user icon size. I've also left the smaller function that uses a regex to sort out the urls since they all differ between the github info components. I can add them into the hook if needed.

The custom hook is wrapped inside the "Posts" component since it's the main component all the other components live inside and thus will be the only ones that need access to the context values provided.

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]

Looks good, but let's shift the URL parsing into the provider.

[aserputov]

@HyperTHD hm, something wrong with prerendering "/about" page . 🤔

[AmasiaNalbandian]

Running another set of tests for the workflow just to be sure, but the e2e is failing. Looks good on deployment though.

[HyperTHD]

e2e tests breaking on a page I never touched is disappointing. Will investigate this

[humphd]

cc @TueeNguyen

> Build error occurred
Error: Export encountered errors on following paths:
	/about
    at /frontend/node_modules/next/dist/export/index.js:499:19

This is the same bug that was reported in Slack with docker builds on master.

I'd say master is currently broken, cc sheriffs: @sirinoks, @aserputov. We may need to figure out what needs to get downgraded or backed out. My first guess is a recent update of next.js? This needs research, as it will start to break everyone.

[aserputov]

@HyperTHD now it's working, can you please rebase this and we will merge it 🙂

[HyperTHD]

@HyperTHD now it's working, can you please rebase this and we will merge it 🙂

Rebased and ready to be looked at

[aserputov]

I still see five commits, can you re-check it please ?

[aserputov]

@humphd Can I just 'squash and merge' or the PR owner should do it ?

[humphd]

@HyperTHD can you squash, rebase, and merge this please?

[aserputov]

@HyperTHD Also, I have a question about #2380. Are we going to create another PR for it?