Set container names and update backend dev script to include prisma generate command

[sherryhli]

Ticket link

N/A

Implementation description

• Explicitly set container names in docker-compose.yml so that it is deterministic
• Run npx prisma generate as part of backend's dev script

Steps to test

1. Run the application (important: update DB_HOST in root .env file to be sistering_db)

docker-compose up --build
docker ps

You should see these container names:

2. Check that the prisma generate command ran as part of the backend dev script, you should see logs like this:

backend_1   | Environment variables loaded from prisma/.env
backend_1   | Prisma schema loaded from prisma/schema.prisma
backend_1   |
backend_1   | ✔ Generated Prisma Client (3.3.0) to ./node_modules/@prisma/client in 1.10s
backend_1   | You can now start using Prisma Client in your code. Reference: https://pris.ly/d/client
backend_1   | ```
backend_1   | import { PrismaClient } from '@prisma/client'
backend_1   | const prisma = new PrismaClient()
backend_1   | ```

You should no longer see this error:

error TS2305: Module '"@prisma/client"' has no exported member 'User'.

What should reviewers focus on?

• N/A

Checklist

• My PR name is descriptive and in imperative tense
• My commit messages are descriptive and in imperative tense. My commits are atomic and trivial commits are squashed or fixup'd into non-trivial commits
• I have run the appropriate linter(s)
• I have requested a review from the PL, as well as other devs who have background knowledge on this PR or who will be building on top of this PR

[albertlai431]

Works for me!