Add support for a deepMatch parameter

Add support for a logical deepMatch parameter to control whether or not the parser uses heuristics to salvage a poorly matching address. If deepMatch is true, use heuristics. deepMatch is false by default.

Here is a couple of addresses that score poorly in geocoder/addresses:
`2187 SOUTH ALDER ST S, CAMPBELL RIVER, BC`
`MAYFAIR MALL 3147 DOUGLAS ST, VICTORIA, BC`

The first has a redundant streetDirection, the second an irrelevant building name. These examples look salvagable.

Heuristics should be applied only after the parser has determined that an input address has no good straighforward match and if &deepMatch=true.

The need for heuristics comes from the MOH experience of geocoding all 4.8 million MSP addresses and getting a 6% rejection rate. How long does it take to manually clean up 300,000 addresses? At between one minute and 4 minutes per address, it could take between 5,000 and 20,000 person hours. Implementing automated address salvage could cut this time in half or more.