Handling the word 'block' in addressString

**Issue:**
Including the word 'Block' in an address (to report road accidents) is resulting in incorrect results. Specifically, the word 'Block' is being interpretted as a street name, and the actual street name is interpretted as locality garbage.

**Example:**
The following addressString provides a correct location based on the address range of that highway segment.
> 800 Trans-Canada Highway, West Vancouver, BC

The following addressStrings provide a location in a different locality.
> 800 Block Trans-Canada Highway, West Vancouver, BC
> 800 Blk Trans-Canada Highway, West Vancouver, BC

**Task:**
Is it possible to enhance the BC Address Geocoder to handle this use case without impacting other aspects of the parser?

Start by locating the addressString parsing entry point and any tests covering BC addresses or address ranges. Reproduce the three examples from the issue and trace how “Block” and “Blk” are classified. Done means both forms resolve like “800 Trans-Canada Highway” without changing unrelated address parsing behavior.

Written by the indexing model from the issue text.