fix: Consolidating Common Data Models

[matt-franklin225]

Description

Implemented the following changes to remove redundant code across the API codebase:

1. Created helper functions for each HTTP status code response (200, 404, 422, 500) to clean up a large amount of repeated code in apps/api/src/rest/routes, adding these helpers into apps/api/src/schema/base/response.ts.
2. Designed base schemas for take, skip, and cursor, which are used several times across apps/api/src/schema/base. The base schemas are declared in apps/api/src/schema/base/search-modifiers.ts.
3. Added several more base schemas across several files in the same directory to remove many redundant lines from the declaration of near-identical schemas.
4. Removed redundant declarations of GE Categories in the schema.

Related Issue

Will close #142

Motivation and Context

This cleans up redundant code in the codebase, improving readability and adding helper functions and exported variables to improve future work.

How Has This Been Tested?

The changes have been tested on a local instance.

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code involves a change to the database schema.
• My code requires a change to the documentation.

[laggycomputer]

(idk why it saved my old comment here, removed because it's stale)

[laggycomputer]

@matt-franklin225 For your benefit, #300 is about to move the list of term names out into stdlib, which may have wider consequences.

[laggycomputer]

You should apply your changes to the new dining API, then we should merge this before it gets too big.

[matt-franklin225]

Added new response helper functions to dining.ts in rest/routes, let me know if there's any other things I need to edit with regards to dining

[laggycomputer]

Minor thing: isCursor should be an optional field in an object. Formal parameters with default values get messy if you ever want to have more than one.

[matt-franklin225]

Worth noting that I had overlooked a 400 response (of which there is currently only one) when creating the functions for routes. I used the response404 function for it since they work identically, but it's worth considering either making a new function called response400 (which would be redundant as it's the exact same as response404) or renaming response404.

[laggycomputer]

Worth noting that I had overlooked a 400 response

Good catch. We probably shouldn't have introduced a 400 to begin with.