#181 upload report endpoint

[tsudhakar87]

ℹ️ Issue

Closes #181

📝 Description

• Added a GET /reports/upload-url endpoint that returns a presigned url
  • basically frontend/client will send a GET request to this endpoint to the get the url, then send a PUT request to that presigned url with the file name + content
• Added a POST /reports endpoint that inserts s3 url to db
  • after sending the get and put requests, the frontend/client will send a POST request to also insert to the db
  • so if we want to retrieve a specific report we can retrieve the s3 url from the db, then fetch that s3 url to get the actual file content that's there
• Modified the previous endpoint that generated reports to be POST /reports/generate

✔️ Verification

• added tests

Local Verification Process

1. Start the stack from apps/backend/ with make up
2. Register a new user via POST /auth/register
3. Verify email via POST /auth/verify-email using the code sent to your inbox
4. Log in via POST /auth/login and copy the AccessToken from the response
5. Decode the token at jwt.io and copy the sub field
6. Insert your user into Docker's postgres using docker exec -it branch-postgres psql ... —
   must use docker exec not local psql since there are two postgres instances on port 5432
7. Make yourself admin in the same way (UPDATE branch.users SET is_admin = TRUE)
8. Open http://localhost:3005/reports/swagger and authorize with Bearer
9. Test POST /reports with a fake objectUrl — no AWS credentials needed
10. Verify the report appears in GET /reports
11. GET /reports/upload-url validates auth/params without AWS, but returning a working
    presigned URL requires real AWS credentials in .env

🏕️ (Optional) Future Work / Notes