fix: editor contains previous comment when reloading page after successful comment to a proposal

[petersalomonsen]

• test for large proposal comment
• test that the submitted transaction contains the pasted comment text
• test that the comment appears in the log
• test that the comment editor field is cleared after successful submission
• test for reloading the page, check if the comment editor field is still empty ( which it is not )
• fix implemented for devhub.near
• fix implemented for events-committe.near by copying in the affected files as is, and running the proposal comment test suite in the workflow. Consider symlinking identical component files in the future
• fix implemented for infrastructure-committee.near by applying the relevant changes into infrastructure component sources. The sources have diverged too much from devhub, so not possible to just use the devhub components as is. The same test suite for proposal comments are also applied to IC.

infrastructure-comment-draft.mp4

events-comment-draft.mp4

devhub-comment-draft.mp4

fixes #876

[petersalomonsen]

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

[race-of-sloths]

@petersalomonsen 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

Reviewer	Score
@Tguntenaar	3

The average score is 3

@petersalomonsen 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]

@race-of-sloths score 3

[race-of-sloths]

🌟 Score recorded!

@Tguntenaar, thank you for scoring this pull request in the Race of Sloths!

[Tguntenaar]

LGTM

[race-of-sloths]

✅ PR is finalized!

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

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

[Tguntenaar]

@petersalomonsen this change is not in the CI only locally. These tests don't work for the events-commitee.near account, that is why I added events/proposals.spec.js.

[petersalomonsen]

good point, I did separate out the proposal comment test and added a workflow task for that as you can see here: https://github.com/NEAR-DevHub/neardevhub-bos/blob/main/.github/workflows/continuous-integration-workflow-events.yml#L22, but I forgot to set it for the whole proposal directory which I believe also will work. Will do so in the next PR ( #888 ).