Add events committee to main branch

[Tguntenaar]

Resolves #842

As part of issue #777

Check list

• None of the deployed components to the events-committee.near account change.
• Github Action that runs the CI for both devhub and events comitee repository.
• Docs are updated

In the next phase of issue #777 we can unify proposal tests in 1 file. By editing the playwright config projects testMatch cases like this: /(proposal|events)\/.*.spec.js/,. I've skipped it in this PR to closer resamble @Megha-Dev-19 her changes in issue #843.

This PR

• Adds the code from the events-committee branch into the main branch.
• Edits proposals.spec for future merging of all proposal tests into a single file instead of 3 seperate once.

I found that the events-commitee is not up-to-date with the main portal so I removed those tests from the proposals. We should make those changes in another PR. (Once this one is merged to chop it in up in smaller bits)

Adding variables

• NEAR_EVENTS_SOCIAL_ACCOUNT_ID
• NEAR_EVENTS_SOCIAL_ACCOUNT_PUBLIC_KEY
• NEAR_EVENTS_SOCIAL_ACCOUNT_PRIVATE_KEY
• NEAR_EVENTS_SOCIAL_DEPLOY_ID

We will need to update the events-commitee.near contract as well before adding these keys. We don't want to deploy the front end with breaking changes.

Future PR

• has to add the clean URL that @petersalomonsen added
• relevant mentions that I've added
• sync @Megha-Dev-19 her KYC updates

[petersalomonsen]

So as we discussed in the call, we will need:

• A separate copy of the CI workflow targeting the events committee instance ( running the tests that are relevant )
• A deployment action that does diff ( dry-run ) when not on the main branch

[Megha-Dev-19]

LGTM, but I see some tests are failing.

[Tguntenaar]

@race-of-sloths please, include my PR in the race!

[race-of-sloths]

@Tguntenaar Thank you for your contribution! Your pull request is now a part of the Race of Sloths!
New Sloth joined the Race! Welcome!

Current status: executed

@Tguntenaar check out your results on the Race of Sloths Leaderboard! and in the profile

What is the Race of Sloths

Race of Sloths is a friendly competition where you can participate in challenges and compete with other open-source contributors within your normal workflow

For contributors:

• Tag @race-of-sloths inside your pull requests
• Wait for the maintainer to review and score your pull request
• Check out your position in the Leaderboard
• Keep weekly and monthly streaks to reach higher positions
• Boast your contributions with a dynamic picture of your Profile

For maintainers:

• Score pull requests that participate in the Race of Sloths
• Engage contributors with fair scoring and fast responses so they keep their streaks
• Promote the Race to the point where the Race starts promoting you
• Grow the community of your contributors

Feel free to check our website for additional details!

Bot commands

• For contributors
  • Include a PR: @race-of-sloths include to enter the Race with your PR
• For maintainers:
  • Assign points: @race-of-sloths score [1/2/3/5/8/13] to award points based on your assessment.
  • Reject this PR: @race-of-sloths exclude to send this PR back to the drawing board.
  • Exclude repo: @race-of-sloths pause to stop bot activity in this repo until @race-of-sloths unpause command is called

[Tguntenaar]

@Megha-Dev-19 the tests are fixed.

[petersalomonsen]

Great @Tguntenaar Let's get this updated with the main branch, and merged as soon as possible!

[race-of-sloths]

🔄 The PR has been merged.

Important

This pull request is a part of the Race of Sloths and has not been scored yet. Scoring will close in 24 hours! 🕰️

[race-of-sloths]

✅ PR is finalized!

Your contribution is much appreciated with a final score of 0!
You have received 10 (0 base + 10 weekly bonus) Sloth points for this contribution

Another weekly streak completed, well done @Tguntenaar! To keep your weekly streak and get another bonus make pull request next week! Looking forward to see you in race-of-sloths