Discovery on application package structure to inform attachment architectural decisions

[mxk0]

Summary

Opportunities have two categories of attachments: NOFO files and the application package. For our Quad 2 goals, we are making all NOFO files available to users on Simpler's opportunity listing page. The application package is not in scope for Quad 2.

That said, application package attachments should likely be stored and handled similarly to NOFO files in the data model. To make sure our architecture also accommodates application packages, we should do some discovery as part of our architectural planning for NOFO files.

Acceptance criteria

• Discovery complete, findings incorporated in NOFO file epic ([Issue #3133] Add auth env vars for login.gov OAuth #3406)

[mxk0]

Notes from JAD: https://docs.google.com/document/d/1kfxAHZscceQU-09ZEn4StuVi_RNq7dvWNzjm_yHRuKo/edit?tab=t.0#heading=h.st2osumxvgr1