Write product spec for Admin interface MVP (Use by Internal Eng)

[thekaveman]

Based on conversation in kick-off scoping meeting on March 8 (notes here)

[thekaveman]

@mrose914 and @angela-tran met to discuss the specific configuration fields that need to be modeled.

Stub spec is here: https://docs.google.com/document/d/1iEumZ5B3mXTaaPRfK1ERlRpSJAmlaQusLOULd2Q27cE/edit#

@mrose914 working to clean up columns on field spreadsheet, working on user stories

[mrose914]

@thekaveman @angela-tran I cleaned up the sheet a bit here: and updated the spec to reflect a Phase 1 MVP that is for internal Compiler devs only.

My thinking is that to move this forward we:

• Review together to discuss and confirm the scope (namely what we include in columns D, F and whether those are MVP)
• Discuss timelines related to other infra decisions that could influence this work (database)
• Decide on how to incorporate Design (eg, I am not sure we fully discussed what Django does and if we want to "implement" a non-designed version first and use that to develop wireframes or something else)

Let me know your thoughts on the plan above and I'll find time for us to sync!

[machikoyasuda]

I wanted to write out in spec-like form what this PR adds to Admin: #1855

• Admin super users (Kegan, Angela, Machiko) as defined in a specific secret, can add email addresses of Compiler employees with a compiler.la email address to the Admin User secret, which will allow these people to log into Admin.
• Users can view models and data. Admin User can view and edit models and data.
• Users who have a Compiler email address listed in the above variable can log into admin at benefits.calitp.org/admin by clicking the Sign in with Google button.
• The Google SSO feature fetches the Compiler email address user's first name, last name, email address and profile icon, which all get saved into the Admin database.