Remove env magic

[3y3]

At current time env is accessible everywhere in project (but used only in main module).

Proposal:

• Disallow env in eslint rules.
• Add 'resolve-options' helper (allow env here).
• Add to options all missed entities. For example const appInstallation = process.env.APP_INSTALLATION; can not be configured without env.
• Reverse default behavior for disableDotEnv
• Make more options accessible from env

Proposal+:

Looks like options.config is a flat object.
Maybe it should be top level param

constructor(options: InitOptions = {}) {}

constructor(options: InitOptions & AppConfig = {}) {}

So most part of configuration will be accessible from env

# appTracingEnabled
APP_TRACING_ENABLED=false

But I understand problems with appSensitiveKeys in this keys.

Most interested api looks like:

import {NodeKit, configure} from 'nodekit';

const nodekit = new NodeKit(configure({
  env: true,
  file: require.resolve('./config')
}));

[resure]

First part of proposal sounds good, except for this:

Reverse default behavior for disableDotEnv

I understand where it's coming from, but in real-life usage that would be an option that almost always would be passed with true value. Maybe we should think about some kind of different NodeKit modes:

1. One without any side-effects (including dotenv, shutdown handlers, etc.)
2. Another for applications, with side-effects enabled

Proposal+:
Looks like options.config is a flat object

It's not, it can contain any type of values, including nested objects.

But I understand problems with appSensitiveKeys in this keys.

Yeah, that's too