feat: allow CLI dev to use injected environment variables

[hmacr]

Closes #509

✅ Checklist

• I have followed every step in the contributing guide
• The PR title follows the convention.
• I ran and tested the code works

---

Testing

• Executed CLI dev command to confirm that it uses the injected environment variables
• Executed CLI dev command to confirm that it uses the env file fallback when the env-var is unavailable

---

Changelog

• Add a generic function to read environment variables from process runtime and env-file for the provided framework. Here, the process runtime takes precedence when a variable is present in both sources.
• Use this function to read TRIGGER_API_KEY and TRIGGER_API_URL.

💯

[changeset-bot]

🦋 Changeset detected

Latest commit: b0de0b1

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 31 packages

Name	Type
@trigger.dev/cli	Patch
astro-example	Patch
@references/job-catalog	Patch
@references/nextjs	Patch
@references/package-tester	Patch
perf	Patch
@trigger.dev/tailwind-config	Patch
@trigger.dev/tsconfig	Patch
@trigger.dev/astro	Patch
@trigger.dev/core	Patch
@trigger.dev/eslint-plugin	Patch
@trigger.dev/express	Patch
@trigger.dev/integration-kit	Patch
@trigger.dev/nextjs	Patch
@trigger.dev/react	Patch
@trigger.dev/remix	Patch
@trigger.dev/testing	Patch
@trigger.dev/sdk	Patch
@trigger.dev/airtable	Patch
@trigger.dev/github	Patch
@trigger.dev/linear	Patch
@trigger.dev/openai	Patch
@trigger.dev/plain	Patch
@trigger.dev/resend	Patch
@trigger.dev/sendgrid	Patch
@trigger.dev/slack	Patch
@trigger.dev/stripe	Patch
@trigger.dev/supabase	Patch
@trigger.dev/typeform	Patch
@references/unit-testing	Patch
@references/remix	Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR