Anywhere that loops over the data in Lambda function should move to CMS

[simonprickett]

Move any looping over data to filter it into the CMS. Endpoints requiring this are:

• traits.json
• readings.json
• starsigns.json

[simonprickett]

Example - for traits, the URL should take a request parameter and the CMS should filter for this without the client code in the Lambda function having to do it:

http://zestyscopes.zesty.site/-/custom/traits.json?sign=Aries

[simonprickett]

Traits might be interesting to do as there's no sign name in the traits as such, it's a lookup based off of the zuid.

[simonprickett]

Done starsigns on the backend, and changed the endpoint name as it's only used this way for mascots e.g:

http://zestyscopes.zesty.site/-/custom/starsignbymascot.json?mascot=The%20Scorpion

Alexa skill code needs updating to use this too.

[simonprickett]

readings.json will also have the same lookup from the zuid challenge that traits currently does.