Reorganize data file structure and add new project partials

Changes

Data Files

Currently, each project (e.g. fh, hs, ht) will maintain a single data .yml but the format + structure across projects differs.

Friday Hacks

past events are kept in archive data files (friday_hacks_<ay>_<semester>.yml)
current events for the semester are kept in a separate file friday_hacks.yml

This means that for each new semester, we will need to (1) create a new archive data file (2) copy from friday_hacks.yml. This is one step too many.

Hacker(school + tools)

events, past or present, are kept in a single data file

Don't see any huge problems with this, but i guess when considering long term, coreteam in 2100 may need to deal with ~10k lines.

Therefore, I propose that we organize events in a per semester structure so that each event team can just work on a single data file.

New file structure: data/<project-name>/<project-name>_<academic-year>_<semester>.yml

e.g. data/friday_hacks/friday_hacks_2223_2.yml

Additionally, there will be no need to have separate file just for current semester's events. This means that we will need to have a way to track what is the current semester in our configs (relevant commit: c877aa54deea0423c0137bdf4322a8734f182e5b), so that we can compute the right data file to reference for each semester.

Partials

Added new partials for hackerschool and hackertools so that we can replace hardcoded templates in index.html
hackerschool and hackertools share the same partials for now, therefore hackertools' partials is a symlink to hackerschool's
Clean up some of the existing partials
- e.g. we were using FH partials for HS so it was pretty confusing

Name	Link
Latest commit	0f875640a6ca0f9f605a1e77d19d56d025ae8241
Latest deploy log	https://app.netlify.com/sites/nushackers/deploys/6471a657db61020008960cc8
Deploy Preview	https://deploy-preview-567--nushackers.netlify.app
Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

nushackers / nushackers-site