Bug in path query handling.

Should have been subbing in "" rather than ":id"
additions to route analysis

Added non-method routes comparison (renamed original to "with_routes")
Added tested routes output
Added rake tasks to output tested/untested routes
Added rake task to clear log and route info as desired
minor cleanup of wording in rake analyze output
Progress towards analysis.

We now include record of an analsys run, with:
- stored percentage
- tested routes
- count of each time route was hit

there is also a rake command to generate the analysis:

rake analyze:tested
addition of d3 graph (largely in progress)

...and a few assorted changes
Analysis cleanup.

Run with:
    rake analyze:tested

OR:
    LogAnalysisService.new(
      analysis_type: "generate_route_diff",
      diff_type: "tested_routes"
    )
storing data on model coverage

not well vetted, but IMO insightful, thus committing.
routes import refactoring, views work in process

- made sure routes import used services as entry point
- deprecated unused routes_import_parent_model, added routes_import_sources
- view work is very much in process

can import routes with:

rake import:routes

or:

ris = RoutesImportService.new(type: "rails")
ris.import
mostly changes to analysis, now completely through service

use:

    rake analyze:tested

or:

    las = LogAnalysisService.new(
      analysis_type: "route_diff",
      diff_type: "tested_routes"
    )
    las.analyze
checking in general progress/basic graphing,

still workin progres
Removing outdated files/clutter
updating note to be more accurate about file deprecation
changing to MySQL2
needed to change some columns to text due to excessive data
Adding a little protection & new class for data clearing methods
removing outdated file
Ability to tag routes/log imports as "ignore" during analysis
adding rake process for tagging imports as "ignore"
Incorporated rails routes into the watcher

and related changes, including scaling back
of the config file, rake processes
Adding revision (release sha/etc) file

Associating it to routes_import, but chose to make it
a separate table/model so we could later include other
information about the release if desired