Implement devcontainer and development docs

[FoxxMD]

• Create a Devcontainer definition with associated compose.dev.yaml stack for configuring local Postgres/Clickhouse dependencies automatically
• Implement VSCode Tasks to facilitate quick project init, building, and running
  • Uses dependsOn to consolidate multiple steps into one EX Init Project task runs Install NPM for all services and server npm run db:push
• Implement VSCode Debug Launch configuration for Backend service
  • Updated Backend tsconfig to generate sourcemaps to enable this. Maps are ignored on docker build
• Added Development page to docs describing non-docker setup/usage and Devcontainer setup/usage

[vercel]

@FoxxMD is attempting to deploy a commit to the goldflag's projects Team on Vercel.

A member of the Team first needs to authorize it.

[FoxxMD]

TODO (maybe?):

• Replace/refactor docker-compose.dev.yml ?
  • Unclear how this is being used currently. The new compose.dev.yaml could replace this if devcontainer development is preferred
  • Also may be good to update this OR provide an additional "dependencies only" stack that only includes postgres/clickhouse so any users developing outside devcontainer can have a minimal reference for dependencies.
• Provide a more minimal .env.example for development?
  • Many of the variables in the prod example aren't necessary for local development, may cause more confusion than they help
  • Some of the variables are hardcoded into compose.dev.yaml since the environment is known
• Allow localhost domain in Rybbit
  • This could be a separate PR as its not specific to development but definitely would help here. Being able to create localhost:XXXX domains would simplify local development as users wouldn't need to mess with hosts or setting up their own dns

[goldflag]

thanks for this. I'll take a look at this this weekend

[goldflag]

@FoxxMD i haven't forgotten about this. i will circle back to this when I have more time