Neighborhood names sometimes contain commas, which messes up CSV API outputs

[jsomeara]

Brief description of problem/feature

Some neighborhood names in Chicago contain commas:

When we request /v2/rawLabels, the commas get included in the CSV without being properly put in quotes, leading to issues with parsing the CSV:

Expected behavior

The commas should be dealt with by putting the neighborhood name in quotes so that csv readers can properly parse the content.

Steps to reproduce

1. Fetch chicago /v2/rawLabels csv file

Potential solution(s)

Add quotes around neighborhood name in the returned CSV

[misaugstad]

Whoops! Looks like we fixed this for most APIs in #3392 but this one was missed! Nice catch @jsomeara!

[misaugstad]

@ananyaa06 if you don't have a neighborhood in your local db with a comma in it, you can just edit the name of a neighborhood in your db to add a comma for testing!