fix: Add yarn pg:build to deployment steps in README

[svenseeberg]

Description

When not creating the PostgreSQL migrations, the yarn build command fails.

Fixes #10496

Demo

Freshly clone the repo and run yarn && yarn build. It will fail. When running yarn && yarn pg:build && yarn build the build succeeds.

Final checklist

• I checked the code review guidelines
• I have added Metrics Representative as reviewer(s) if my PR invovles metrics/data/analytics related changes
• I have performed a self-review of my code, the same way I'd do it for any other team member
• I have tested all cases I listed in the testing scenarios and I haven't found any issues or regressions
• Whenever I took a non-obvious choice I added a comment explaining why I did it this way
• I added the label Skip Maintainer Review Indicating the PR only requires reviewer review and can be merged right after it's approved if the PR introduces only minor changes, does not contain any architectural changes or does not introduce any new patterns and I think one review is sufficient'
• PR title is human readable and could be used in changelog

[rafaelromcar-parabol]

LGTM.

Could you please verify it @mattkrick? I tested locally and it works, as @svenseeberg says, but I'm not sure if we should include yarn kysely migrate:latest and yarn pg:generate to run the same we run in our build procedure.

• Doc today: yarn && yarn build
• @svenseeberg proposal: yarn && yarn pg:build && yarn build
• Build GH Action: yarn && yarn kysely migrate:latest && yarn pg:build && yarn pg:generate && yarn build (ignoring the --no-deps for the doc).

[mattkrick]

LGTM! Soon we'll be rid of pg-typed & just use kysely, but until then...