Re-Architect loading tools into tC core

[da1nerd]

Dependencies of tools created for tC core such as wordAlignment or translationWords are not being installed. The current tools only work by accident because tC core happens to use the same dependencies. We need to redesign how tools are loaded into the core so that tools don't crash if using other libraries.

There are two approaches which could be taken in steps for simplicity.

1. add a script in package.json to install the tool dependencies. This would be fairly easy.
2. Move the tools out of the core and load them from an external location on the file system.

The final step would provide additional benefits:

1. Easy for developers to create and add new tools.
2. Tools could be piped through webpack to entirely remove the concern for dependencies.
3. Tools could be updated apart from the core.

[benjore]

• Core (functions that EVERY tool requires, but no tool business logic)
  • Source content update (Dynamic Source Content Update #3175)
  • Project import/export
  • Data persistence
  • Network access
  • Menu bar (night colored)
  • Actions menu
  • Stepper/Home
  • Alerts
• Independent NPM modules
  • Business logic required by MULTIPLE tools or Core (each an NPM module)
    • Selections (M)
    • Word alignment helpers (L)
    • Tokenization
    • Word-map
    • USFM
    • tC tool
  • tC UI-ish toolkit (one NPM module) [initial setup] (L)
    • Scripture pane (L)
    • Scripture pain plugin - HOC (L)
    • Verse check (L)
    • Verse editor (M)
    • Menu (M)
    • translationHelps code (s)
    • Comment (M)
    • Bookmark (S)
    • Checkinfo card thingy (Smurf bar) (S)
  • Tool - Business logic not required by any other tool
    • tW (would need rewritten to use above components) (L)
    • tN tools (already need rewritten)
    • Alignment Tool (L)
• One abstract interface in tC tool (needs architected/designed)