Support viewing of Condo node order and storage order requests

[matthew-li]

Users should be able to see the statuses of their Condo node purchase orders and Condo storage purchase orders on the website, and receive status updates about their requests.

[wfeinstein]

Start to draft the workflow, which will take sometime to finalize.

1. PI contacts BRC to express interest in buying in hardware. The communications typically start outside the portal, including providing quota, nail down hardware type/feature and amount.
2. Once the PI makes decision, PIs will submit condo purchase request on the portal including what/amount to buy, Charstring (BRC) or PID (LBL). I think designated system admins get notified. ( e.g. Gary, Ken, Wei, Tin....)
3. Procurement process, including date of submitting order, details of the order (requisition number, vendor name, node feature and amount), BRC has its internal order tracking system, such as ADMIN-3482 needs to be tracked, requester, PO/Pcard, date of receiving order and etc.
4. Installation process, including the status of installation of physical nodes, cable, node provision, account request from PI, slurm setup.
5. Ready for usage

[matthew-li]

Copying in Wei's notes from #547 to merge the two issues:

Start to draft condo storage procurement, which will take sometime to finalize.

1. PI contacts BRC to express interest in buying in storage. The communications typically start outside the portal, including providing quota, nail down storage size.
2. Once the PI makes decision, PIs will submit condo purchase request on the portal including what/size to buy, Charstring (BRC) or PID (LBL). I think designated system admins get notified. ( e.g. Gary, Ken, John, Wei....)
3. Procurement: typically extra storage is also available for purchase.
4. Installation process, including the status of storage provision.
5. Ready for usage

[matthew-li]

For now, we're not thinking of allowing users to make purchase requests from the website--this process is complex, and requires a lot of back-and-forth with staff through various channels (email, ServiceNow, meetings).

Rather, after the request has been made, staff will enter the information about the request into an external data source, which MyBRC/MyLRC will read from. (Right now, we're thinking of a simple spreadsheet for this data source, since it's intuitive for staff to work with, but I'm open to suggestions on this.)

PIs (and designated points-of-contact) should be able to see their requests on the website.

Ideally, users would also receive email notifications when the status of a request changes, but this is less high priority than the basic ability to log in and see the status on the website. (This notification requirement will likely affect the design of the feature, so worth keeping in mind.)

[matthew-li]

Some existing code that uses gspread to read from a Google Sheet: https://github.com/ucb-rit/coldfront/blob/master/coldfront/core/project/utils_/renewal_survey/backends/google_forms.py