Add support for an input field called streetAddress for more accurate batch geocoding

Client management applications and data warehouses extract and transform addresses to run through the batch geocoder. Typically, these sources keep addresses in pieces instead of in a single address string and these pieces often include locality. If a single address string is given to the batch geocoder, the geocoder often comes up with too many meaningless interpretations that involve variants of locality. If locality is kept separate on input, these meaningless interpretations can be avoided. The parser can still look for locality aliases and correct spelling mistakes in locality names, it just won't misinterpret parts of locality names as street names (e.g., Rupert St, Port Hardy,BC instead of Prince Rupert, BC)

Add support for specifying an input address in the following format:

**streetAddress locality provinceCode**

streetAddress includes all elements of addressString except locality and provinceCode.

Start by tracing the batch geocoder's handling of addressString and the parser entry point; the issue identifies the new streetAddress locality provinceCode input shape. Compare it with existing addressString handling, then verify that locality remains separate and the documented format avoids the cited ambiguous interpretation.

Written by the indexing model from the issue text.