Add support for route partition metrics in test case framework

[mraross]

We propose the following partition metrics:

1. Truck Partition Signature - a character string of binary digits indicating partition type (eg., 0 means non-truck partition and 1 means truck partition). Here are some example partition signatures:

   "01" means non-truck-route (ntr) to truck-route (tr) "10" means tr to ntr "010" means ntr to tr "0101" means ntr to tr to ntr to tr

   Partition signatures can be computed from the partition list returned by the current route planner.

2. truck-partition-count - the number of truck partitions in the route; derived from the partition signature.

3. non-truck-partition-count - the number of non-truck partitions in the route; also derived from the partition signature.

We can use these metrics to compare TransLink benchmark routes to route planner routes.

TransLink has proposed that a good truck route has the partition signature "010". We suspect "0", "1", "01", "10", and sometimes even ""0" can reflect good truck routes. Note that when a route is found to not be a good route, the root cause more often bad data

[mraross]

"0" - from 49.24271,-122.84843 to 2347 Como Lake Ave, Coquitlam, BC looks good. truck route multiplier = 13 or 10.

[mraross]

"010" from 49.24271,-122.84843 to 121 Mundy St, Coquitlam, BC doesn't look good. trm=13

but with trm=10, its good again:

[mraross]

2682 Finch Hill, West Vancouver, BC to 121 Mundy St, Coquitlam, BC trm>6

[mraross]

2682 Finch Hill, West Vancouver, BC to 121 Mundy St, Coquitlam, BC trm<7

[mraross]

Verified