`Evaluations:` architecture bug check

[Andyvargtz]

Context?
FormData is currently used as a "submisison form" for each of the programs a Projects is candidate of and holds a scoped context in which the project should be evaluated (hackathons, buildgames, grants, etc). Form Data also serves as the middle storing layer for the additional questions on a submission form (ex. custom data of a Game, etc). See it as a program data that complements the info Project profile info.

What is the problem:
Evaluations done through /events/[id]/evaluate are attatched to Project in DB.

Why is a problem
Currently all comments in evaluate are attatched to the "parent-level" Project, instead of pointing to the program evaluated (Form Data)

How to solve

• During Project Submission creation process: Enforce the creation of a FormData ("project application") tied to the project that will set origin to be "hackathon" and including the additional form_data

        {
          "project_id": "<project.id>",
          "origin": "hackathon",
          "form_data": { 
                      "hackathon_id": "<project.hackaton_id>",
                      "submission_data"
           },
          "timestamp": "<hackathon.start_date or now>",
        }
  

• Each evaluation under /events/[id]/evaluate should point to the formData of the formData that matches the hackathonId

• Backfill:
  Currently every submission has created a new project entry, so for projects with no FormData, backfill to add a FormData with the origin to be hackathon ID. (All BuildGames originated projects should already have a FormData in). If a hackathonid is empty it should have the origin set as "review" for identification.

Submission