CT CT182A concurrency is not signed

[cl94]

In the database, CT Route 182A is shown as having a concurrency with Route 183, allowing it to return to Route 182 on both ends. As of 2 hours ago, no signed concurrency exists in the field. All signage indicates that 182A ends at its intersection with 183 in Colebrook Village, with the section of 183 between 182 and 182A being signed only as 183.

While the 182A/183 concurrency IS official, it is unsigned. While I personally have no problem with including an unsigned route, I do believe that we should be consistent.

[yakra]

https://github.com/TravelMapping/HighwayData/pull/2302