feat: add reactions and comments to v0.4 proposals

[R-K-H]

{
"level": 50,
"time": 1746472054863,
"pid": 2,
"hostname": "da734c288446",
"name": "API Server",
"module": "reaction controller",
"err": {
"type": "DatabaseError",
"message": "insert or update on table "reactions" violates foreign key constraint "reactions_proposal_acct_proposals_proposal_acct_fk"",
"stack": "error: insert or update on table "reactions" violates foreign key constraint "reactions_proposal_acct_proposals_proposal_acct_fk"n at (/app/node_modules/pg/lib/client.js:535:17)n at processTicksAndRejections (native:7:39)n at (/app/node_modules/kysely/dist/esm/dialect/postgres/postgres-driver.js:92:41)n at processTicksAndRejections (native:7:39)",
"length": 367,
"name": "error",
"severity": "ERROR",
"code": "23503",
"detail": "Key (proposal_acct)=(DGdwQnrn3QP3amEhmrKUBeGc4TbmZdWEjG5XwFqReHJx) is not present in table "proposals".",
"schema": "public",
"table": "reactions",
"constraint": "reactions_proposal_acct_proposals_proposal_acct_fk",
"file": "ri_triggers.c",
"routine": "ri_ReportViolation"
},
"msg": "Failed to create reaction"
}

[R-K-H]

To do this we need to rethink the relationships and how that can / should work. Given these are new tables and might be new tables moving forward for each version.