small cleanups

removing the singleton scope from resources that had it, preparing to time some stuff to see impacts
removing an errant sysout
adding a way to configure resource properties via the configuration.

not totally hooked up yet, but the mechanism works and is tested.  next
step is to use it!
using the configured resource settings

needs a little more refactoring but the system basically works.
basically.  however it's not very DRY and not super well tested.  yet.
but I have... a... plan
drying up the ResourceSettings determination

which is good! cause the rules are about to get more complicated
further refactoring

loading resource settings logic is now correctly centralized and tested,
and the system is ready to accept overrides.

however first I need to dry out the default configurations so they are
defined in one place and used for both config-free and
config-with-default scenarios
renaming default providers for consistency
tightening up the API
adding the notion of JSON modules

for one, apparently node does this.  for another, it's a simple way to
get to raw data for the resource configuration. i'm sure it'll be handy
in other ways later.
report module loading errors
reading the resource configurations from a single source

DRY IT UP! woo woo.
removing the first shot at per-resource configuration

while i think about it. it definitely isn't right yet
adding an interruption facility to tasks

task interruption can be used to break out of loop tasks that are
waiting on some sort of JDK API, which generally speaking cannot be
worked around.
making the resource watch service configurable/restartable

welcome to the 21st century, watch service!  mainly this is to support
the idea that configurations will be per-environment, and
programmatically updateable in that regard, i envision something like

var env = ('jj/env');
var rc = require('jj/resource-configuration');
rc.watchFiles(env.STAGE == 'Development');

or similar.

this doesn't include the actual script piece yet!  haha
allow configurations of file watching via config.js
testing resource configuration

and the corollary, fixing the bugs it uncovered.  lol
adding an API to read environment variables

in a javascripty way that is.  noticed a weird issue - continuations
inside an array forEach fail.  this will be painful! i'm going to have
to investigate that
adding system properties

name clean-up on the environment exposure as well
figure out the repl test failure

naturally, it was a problem of determinism

this test actually needs some expansion, but that's true of the REPL
system in general.  the fact that it runs at all is pretty neat,
honestly.