fix: address conflicts with ENV/script/process names

[tigris]

devbox plugin docs suggest to use ENV vars whereever possible for config, as this will allow users to override things where needed

I think we should reduce use of init_hook where possible since it runs every time you enter the directory (assuming direnv allow is on)

SELF NOTES for picking back up:

• use path:/Users/path/to/plugin to include your own copy
• I'm not entirely sure as yet how to make devbox pull in your changes after you make updates to the plugin - but renaming the directory and updating devbox.json certainly works

Issues:

• this plugin creates a user, an outbox table and heartbeats in your database by default, but many systems might already have DB migrations for this, considering those need to be created in prod and we usually manage an RDS schema via migrations
• this is especially troublesome in the case of influx because the devbox run populate script uses .sql files that look to be a snapshot of the database post migration (as is the rails standard i believe) - this means on a fresh clone doing devbox services up the plugin would try and create tables and users before other things have had a chance to setup the database
  • perhaps we need a config option (env var?) that tells the plugin not to bother creating psql resources (we already did it, it's part of our database migration workflow)

[abrokenjester]

LGTM.