chore: package invocations with dotenv

[AmberFryar]

The --env-file=.env CLI flag was necessary for local development so it could discover the version tags and run tests. dotenv dependency has the same effect, except that it is a runtime import. This allows for the invocations to be functional without the CLI flag. Because of the timing difference between dotenv and the CLI flag, imports on vitest and astro config were necessary. The end result is the same, but this dependency allows for a cleaner implementation.

[netlify]

✅ Deploy Preview for pepr-docs ready!

Name	Link
🔨 Latest commit	3b3fd74
🔍 Latest deploy log	https://app.netlify.com/projects/pepr-docs/deploys/698372d79675990009f26f7b
😎 Deploy Preview	https://deploy-preview-199--pepr-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 90 (🟢 up 24 from production) Accessibility: 94 (no change from production) Best Practices: 83 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[samayer12]

This PR adds dotenv, but I don't see a .env file as part of the project. Do we expect devs to maintain their own .env file outside of version control?

[AmberFryar]

This PR adds dotenv, but I don't see a .env file as part of the project. Do we expect devs to maintain their own .env file outside of version control?

@samayer12 Devs currently (before and after this change) need a .env to set the CORE path. The local clone of Pepr allows semver to find the git tags for the versions for development.