Implement "chapter" field in schemas

[kenetec]

Summary
To implement cross-chapter usage, we will need to add a "chapter" field to some of our schemas.

Problem/Current Functionality
The recruitment portal was designed for one chapter, however, many chapters can benefit from this product. Right now, there is no way to delineate between chapters.

Solution

1. Add a "chapter" string field to:
   • User
   • Workspace
2. Edit the calls to the db to make sure chapters match.
3. Edit /userRoles endpoint to allow for chapter to be updated.
4. Add chapter column in adminRoles page.

Acceptance Criteria / User Stories

• As a director, I should be able to:
  • Set the chapter of a user.
• As a user, I should see only resources that are specific to the chapter.