fix: ISEB is not included in buildingCatalogue.ts

[KevinWu098]

We sourced our data in buildingCatalogue.ts from https://classrooms.uci.edu/classrooms/, but their directory doesn't include ISEB. There are indeed courses hosted in ISEB (although few), and it's a popular spot to study/have events, so custom events may want to use ISEB as a location.

We should add ISEB to our list; whether we manually create that data point or find a new, more comprehensive list can be at the PR's discretion

Implementation

Relevant Files

1. We have a file apps/antalmanac/tools/catalogue_builder.js which scrapes https://map.uci.edu for all of the locations currently available.
2. catalogue_builder generates a file which we have in apps/antalmanac/src/lib/buildingCatalogue.ts which is a mapping of IDs to locations
3. At the same time, we have another file /Users/kevinwu/Documents/Code/ICSSC/AntAlmanac/apps/antalmanac/src/components/RightPane/SectionTable/static/locations.json which is a mapping of locations to IDs.

Your Task

1. These three files are tightly coupled, and should be placed together. I'd recommend moving them all to a directory in apps/antalmanac/src/lib, maybe name it locations
2. Then, modify catalogue_builder to be camelCased, in Typescript, AND to build both buildingCatalogue and locations.json at the same time.
3. Lastly, make sure that locations.json is a properly typed TS file, rather than JSON
4. All tests in locations.test.ts should pass. There should be no need to edit this file, but you're free to if it serves a purpose.

From user feedback:

ISEB does not exist as a location.

[vinnyho]

Hi could I take this

[KevinWu098]

Reopening Issue -- we should be updating our catalogue via our scraper, not manually

[MinhxNguyen7]

Where would we scrape it from, though?

[MinhxNguyen7]

This issue should be closed, and the scraping option, if feasible, should be a new issue. This is just the "good first task" bug

[KevinWu098]

On mobile, but we have a scraper that hits https://map.uci.edu

[KevinWu098]

This issue should be closed, and the scraping option, if feasible, should be a new issue. This is just the "good first task" bug

Im fully aware that I'm being rather pedantic about this, but this issue hasn't really been resolved properly -- we don't manually insert location entries.

I'd rather not revert the PR, but the issue frankly was not resolved appropriately (which is my fault as I did a poor issue write up)

[KevinWu098]

The scraper is already implemented, and just needs to be run. We shouldn't be manually inserting.