Add development_dep: byebug
TenseBlock: support #each
Begin `querent` implementation

Begin the creation of a "querent:" a delegate that
bears all the flexible method lookup resolution
logic.

We also comment-out paradigmatic_verbs require.  This
refactor is challenging, paradigmatic_verbs
loads up all types of verb types whose migration
to the 'querent' interface may not be complete.
Formatting
Implement Querent interface

1. LatinVerb: responds to #querent and delegates
that call to `@tense_method_applicator` which
supports `#querent`. Internally, it uses a
`QuerentFactory` which brokers the selection
of a `Querent` subclass (each _regular_ verb
type).  The returned TenseBlocks then are then
thrown to a "vectorizer" that adds the
permutations of person and number to look up
specific values in the returned `TenseBlock`.
Add MutatorForClassificationFactoryForQuerent

Based on the classification, some verbs require
tampering with their tenses i.e. they are
present only.  Create a factory that knows which
mutation set to apply (Regular e.g. would have a
no-op mutation; PresentOnly, a rather serious
mutation).
TenseMethodApplicator: Prune tenses if Present-only
Encapsulate vectorization logic for Third conjugation
Create "TODO" file todo.txt
TenseMethodApplicator: Refactor: Extract frobnicate_the_querent!

Mutations to the querent should be encapsulated in
a single oddly-named method (for the time being).
Rake::TestTask: Add byebug, Minitest::Pride
[FAIL] Move querent calculation from TenseMethodApplicator to LatinVerb
Remove Invariant mutator, obviated by MutatorForClassificationFactoryForQuerent
Semideponent mutation should happen on querent, not verb
Stub LatinVerb#prepare_querent!
Querent from tense_method_applicator to LatinVerb
rm LatinVerb#prepare_querent!
Move querent factory from tense method applic to
LV
actually remove mutator for classif. factory
Move conjugation-specific tense block calculation to LV from TenseMethodApplicator