Extract getProfileData into a separate place

[allthesignals]

naming is not low hanging fruit if you ask me! I definitely think profile qp should become profileName

also, happy to extract the getProfileData into a separate place. I extracted it b/c i was thinking it could be repurposed in a route that does not require a selection ID but rather accepts a list of geoids -- wouldn't be used in the front end, but could be useful to people like that grad student that emailed & wanted to scrape a bunch of profile data; they could programatically hit that route, esp if we allow 'compare' to be optional. but I agree that I don't necessarily love the idea of this living in a util. Let's think about where else this could go ?

Originally posted by @julialucyhogan in #68

[allthesignals]

Issue moved to NYCPlanning/labs-factfinder #752 via ZenHub