longest() and oneof() operator takes boost::shared_ptr<std::vector<boost::shared_ptr<ConjConditions> > >

So it's clear it's not about MatchRule at all.

1) MatchOperator was essentially a wrapper for "match" section of "apply" operator
2) Other operators like Repeat actually used ConjConditions directly, without using MatchOperator
   - so ApplyOperator could too!
3) The confusion was about "match" referring both to part that is matching
   sentence against match conditions, and the results of this matching process.
   That led e.g. to "match_operator" rule in grammar, which was unlike
   "strset_operator" rule and the like. "match_operator" was about
   the "match" section in "apply" and now it is more straightforward.
   Next step should rename "match_fit" to be actual "match_operator",
   consistent with "XXX_operator" for other XXX types.

Also, adding M in grammar to be shorthand for $m:_M (vargetter) op in match context.

fix crashes in markmatch / unmarkmatch caused by taking a reference to a shared pointer instead of just making a copy, and a typo

Basically a ParsedExpression wrapper for Variables and ApplyOperator.

MatchVector, AnnotationMatch, TokenMatch are now MatchData
MatchData is value_type of Match which now has get_value/set_value
Match has also copy construction working properly now
Default value for Match holds MatchVector so adding $m:_M var in grammar works as intended.