Officer data: Update officers.json and tiers.json

[EthanThatOneKid]

In officers.json, the order that the officers should be listed is determined by a separate Tier (stored in tiers.json) which is referenced by ID.

The officers.json has some rules that should always be guaranteed:

• Officer position tiers should be synced with the appropriate tier ID.
• Officers are listed in alphabetical order in officers.json.

Example updated Tiers:

acmcsuf.com/src/lib/public/board/data/tiers.json

Lines 3 to 4 in 414c3f7

	"Vice President": { "id": 1, "index": 150 },
	"Webmaster": { "id": 2, "index": 200 },

Example updated Officer (using IDs of example tiers above):

acmcsuf.com/src/lib/public/board/data/officers.json

Lines 63 to 68 in 414c3f7

	"positions": {
	"S21": { "title": "Webmaster", "tier": 2 },
	"F21": { "title": "Webmaster", "tier": 2 },
	"S22": { "title": "Webmaster", "tier": 2 },
	"F22": { "title": "Vice President/Webmaster", "tier": 1 }
	}

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
acm-csuf-site	✅ Ready (Inspect)	Visit Preview	Oct 23, 2022 at 5:46AM (UTC)

[karnikaavelumani]

First of all, thank you so much for updating the tiers. This is easy to follow and very clear to understand. There were a couple things that I would like to be clarified:

There were two members who had previously worked as a "workshop manager". Should we include that into the tier list? Perhaps as "Workshop Manager": { "id": 23, "index": 1250" } so we can replace "ICC Representative": { "id": 24", "index": 1300 }. This is simply a suggestion and is not required!

For consistency, I suggest we update the "nodebuds officer" title to "Nodebuds Officer" to reflect the other titles such as "Dev Officer" or "Algo Officer"

[karnikaavelumani]

Looks great!