Update about page on markbind

[gerteck]

What is the purpose of this pull request?

• Documentation update
• Bug fix
• Feature addition or enhancement
• Code maintenance
• DevOps
• Improve developer experience
• Others, please explain:

Overview of changes:

Closes #2881

See: https://deploy-preview-2887--markbind-master.netlify.app/about

Anything you'd like to highlight/discuss:

As much as possible, I have tried to update the manual list of contributors (this is on top of what we have from all-contributors table), adding members that I know of and tracking the timelines based on git commits, PR merges and or PR reviews, as well as sourcing from the nus-cs3281/2 website.

• I also don't have exact detail on team leads and mentors as well as involvement range periods, so apoloigies if my estimates are inaccurate
• Past contributors who would like to update the list for correctness, comment before this is merged, or open a PR after to correct it!

Apologies to any past contributors and team members for any inaccuracies if any! Again, feel free to PR or add yourself through the all-contrib-bot!

Also updated the contact email to nusoss@nus.edu.sg

Also added devdocs step to update about page, ideally at least once a year

Testing instructions:

Proposed commit message: (wrap lines at 72 characters)

Update About Page in documentation

---

Checklist: ☑️

• Updated the documentation for feature additions and enhancements
• Added tests for bug fixes or features
• Linked all related issues
• No unrelated changes

---

Reviewer checklist:

Indicate the SEMVER impact of the PR:

• Major (when you make incompatible API changes)
• Minor (when you add functionality in a backward compatible manner)
• Patch (when you make backward compatible bug fixes)

At the end of the review, please label the PR with the appropriate label: r.Major, r.Minor, r.Patch.

Breaking change release note preparation (if applicable):

• To be included in the release note for any feature that is made obsolete/breaking

Give a brief explanation note about:

• what was the old feature that was made obsolete
• any replacement feature (if any), and
• how the author should modify his website to migrate from the old feature to the replacement feature (if possible).

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 71.35%. Comparing base (8d5c8e7) to head (a49380b).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2887   +/-   ##
=======================================
  Coverage   71.35%   71.35%           
=======================================
  Files         133      133           
  Lines        7229     7229           
  Branches     1712     1712           
=======================================
  Hits         5158     5158           
  Misses       1970     1970           
  Partials      101      101           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[yihao03]

Looks sick i like the designation

[github-actions]

@gerteck Each PR must have a SEMVER impact label, please remember to label the PR properly.