feat: add env init command that copies from template placeholders

[zimeg]

Changelog

A new env init command copies a template placeholder ".env.sample" or ".env.example" file to the ".env" file of a project.

Summary

This PR adds the env init command that copies from template placeholders 🌲

Preview

Included are expected cases and common edges to encounter! 🔬 ✨

⚡ Bolt Frameworks

1. An existing placeholder file is used for the new ".env" file
2. An existing ".env" file is not overwritten
3. A missing placeholder file notes to use "env set" command

🥀 ROSI Features

1. Deployed apps recommend the "env set" command
2. Local development requires selection and saves to project file

Testing

Checkout the changes of this branch and experiment with either a Bolt or Deno app:

$ slack create asdf
$ cd asdf
$ slack install     # Required for Deno - Optional for Bolt
$ cat .env.sample   # Inspect values upcoming
$ slack env init
$ cat .env
$ slack env init    # Reattempt the initilization

Notes

Some follow up remains proposed to improve this but is left out of scope for this PR 🏁

• Prompting for values included in placeholders might be a meaningful improvement to avoid unexpected values. We might find the following format interesting toward this but without much exploration right now:

# COMMENTED_VARIABLE=       # Not prompted
UNCOMMENTED_VARIABLE=       # Prompted
SET_VARIABLE=debug_example  # Not prompted

• Including this command as part of project init ought make setup a breeze it's been said 😉

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

[codecov]

Codecov Report

❌ Patch coverage is 89.71963% with 11 lines in your changes missing coverage. Please review.
✅ Project coverage is 71.69%. Comparing base (f2e54bc) to head (f3508a0).

Files with missing lines	Patch %	Lines
internal/slackdotenv/slackdotenv.go	68.18%	5 Missing and 2 partials ⚠️
cmd/env/init.go	95.06%	3 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #516      +/-   ##
==========================================
+ Coverage   71.56%   71.69%   +0.12%     
==========================================
  Files         224      225       +1     
  Lines       18976    19083     +107     
==========================================
+ Hits        13581    13681     +100     
- Misses       4192     4199       +7     
  Partials     1203     1203              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mwbrooks]

🙇🏻 Thanks a bunch for opening this PR! 🎉 I'm excited to see this one landing.

🧠 Could we swap "template placeholders" for "template file" or ".env template file"? "Placeholder" tends to imply a variable or token that gets substituted, which is a bit ambiguous here. Since we're copying the file verbatim, ".env template file" is more precise and the common convention in the wild from a little Claude research.

[zimeg]

@mwbrooks Apologies for the pause after review 🎁 ✨

The polish to how these concepts landed above and I think it puts this in a better place for ongoing iteration! Let's not think about that right now though. I requested another review for sureness of how this appears 🔮

[mwbrooks]

✅ Thanks for the refactors @zimeg! This PR looks great and works like a charm! 👌🏻

🧪 Manual tests are looking good and unit tests have good test coverage.

📝 A few follow-ups that come to mind:

1. suggestion: We should include env init as part of project init so that the new projects come with a .env provisioned out-of-the-box.
2. question: When no .env exists and we run env set, the CLI creates .env. Should it create a blank .env or use .env.example/sample when it exists? My first impression is that we'd remain consistent if we tempalted from the .env.example/sample.

[mwbrooks]

note: I had Claude do some research on github.com and these are the top 2 placeholder names for .env files and make up the largest percentage. So, I think this is a great start!

[mwbrooks]

praise: error code prefixes for clean organization! 🎉