Add Paths Endpoints and Draft Page Scaffold

[alexfinnarn]

The Fund resource has a "paths" route the frontend uses to build fund pages. Most of the "pages" on giving.cu.edu are under the "/about-us" prefix. However, we will start out with simply a "/pages" prefix for now.

Pages on the current site either have the 2020 impact report in a sidebar-right area or are one-column with no sidebar-right. I originally thought the sidebar field would be a good fit for rich text, but since it's all the same thing...and making models/objects/attachments to handle this would be a PITA. The simple solution, for now, is to tie keys to actual markup.

Acceptance Criteria

• [ ] Add paths/[:model] endpoints to standardize on providing paths to the Next.js frontend
• [ ] Add rudimentary Page scaffold with rich text area for content field

[alexfinnarn]

I ended up coding the pages in the frontend repo since it quickly got complicated translating rich text area output between backend and frontend. Sharing global base styles helps, and I did find a Tailwind CSS Typography plugin that adds styles to the markup you don't control, like WYSIWYG.

However, it made more sense to decide on the frontend styling and layout first vs. trying to get the WYSIWYG or layout builder working before even getting to what those UI tools should end up outputting.