Adding Approval Process for Hack for LA Project Updates

### Dependency
Specs need to be collected

###Overview

We need to build a project page change request and approval workflow in VRMS so project leads can submit updates, reviewers can approve or reject changes, and approved requests can be automatically routed for implementation, eliminating the current manual GitHub-based process.

The Ask:
Bonnie requested a feature to have an approval process built into VRMS so PMs can request changes to their project webpages.

- Option 1: review and approval process, and route to a developer once fully approved.
- Option 2: Bonnie would have option to edit or reject with reason, and route back to PM.

Current State:
The GitHub page is an issues page for the website so people can propose relevant changes to the website – Bonnie reviews this, approves, and developers can update.

The approval process can be automated and ultimately it sounds like once approved, it can get kicked over to a developer, instead of Bonnie facilitating next steps.

Acceptance Criteria:
- Bonnie can approve, edit or deny changes with reason on the project page in VRMS
- End-to-end review process & with approved designs for screens
- Routes to developer for implementation if approved
- Routes to PM if denied
- PM is alerted if Bonnie makes an edit and approves

We are creating screens with the same features from the existing process to migrate that process to VRMS. Once those features are rolled out – all PMs will be directed to VRMS to request these updates and the Github process shuts down. Changes will happen moving forward in the VRMS database.

### Action Items
Need to map out:
-What is the review process like
-What do the screens look like
-What is the approval process is
-What happens if you only approve 3 out of 5 things for example; can we selectively approve?
-What happens if something is not approved?
-Does this go back to the originator? How? This needs to happen automatically in the system itself