Change comment/pin types to use just 3 types.

The comment and pin types are no going to just be MARKER, COMMENT or
ADMIN. And that's it. This commit updates the constants as well as the
readme for documentation purposes (RTFM&&STFU||GTFO) and also fixes
the spider to run correctly given the new circumstances.

This commit is part of preparation for a release of API version 3. Which
will have these new types and will also include:

- Types of just MARKER, COMMENT and ADMIN
- Proper entity counting as per @the-hobbes
- Deletion of comments support through the api by comment id
- Deletion of pins support through the api by pin id (and deletion of
  any comments associated with this pin)

For development purposes the appspot domain at greenupapi.appspot.com
will switch to using version 3's in progress version. You can see what
version of the api you're using by querying the /api endpoint and noting
the version number. The stable version is 2-5 so the
greenupapp.appspot.com will continue to serve that version until the
above features are fully implemented.

If you are pulling down this API version to your local machine you will
_need_ to clear out your old database otherwise you will experience
server errors when asking for comments/pins. If you ask me for
assistance I will point you to this commit and kindly tell you to read
this nice commit message I took the time to write for you.
Bumped API version number

Bumping development version of API version 3. This way clients querying
the greenupapi.appspot.com endpoint can realize that they're not working
with the same version of the api anymore.
Fix #129

Pull develop and try it now @popwarfour
Implementation of Feature #128

Added 'addressed' field to pins. Can be updated through a put request
and is one of the required fields during pin creation. See the
specification in the api folder for details.
Work on deleting Pin by ID. Reference Error.

Having trouble with the reeference property and deleting that. It
doesnt' seem like filtering to get comments based on the pin is working,
I also tried using the pinID but to no avail.

@the-hobbes could you take a look at this? Is it possible to do
something like pin.comments.delete() or something of that nature? For
example, rails has Association.clear / destroy_all which clears our
associations from an object itself. I imagine the app engine must have
something like that that we could use? Or some type of dependent destroy
that automaically is fired off from dekeintg the pin or not to.

To reproduce the error:

- run git fetch origin referenceProperty
- run get checkout FETCH_HEAD
- run the spider, it will pass.
- Run it again. It will fail on retrieving the comments.
- fix the problem if you can ?
- if you fix it: git checkout -b referenceProperty
- git push origin referenceProperty
- send me a pull request or push direcly to the mainline's
  referenceProperty branch or merge it with --no-ff to
  feature/type-clarification branch (which is essentailly the api
  version 3 branch)
Merge branch 'develop' of https://github.com/EJEHardenberg/GreenUp into ios_networking
Fixed the reference Property issue

I am so infuriated with the GAE. This is an ugly hack to fix the broken
reference property. Trying to retrieve the comment that will be broken
when deleting the pin doesn't work. I tried:

filter(pin = the id), filter (pins = the id) doing a ,get() and deleting
just that, not doing a get and iterating and deleting, doing a get and
iterating, etc etc. Nothing seems to work to delete the referenced
comment. So fuck it. There's a try except in the comment creation now
that fixes the issue. It's an ugly stupid hack.
Merge branch 'referenceProperty' into feature/type-clarification
Fix #129

The problem was that we're all morons. I've corrected this with a heavy
dose of sarcasm, hatred, and far too many cups of Tea. Enjoy.

Seriously though, there is no id! there is key() and there is the id()
of the key object. If we were in RoR then there would be an id, but
sadly that would make too much sense. Although, if we were in RoR then
we wouldn't be doing a raw json API server anyway, because that's not
what RoR is designed for and it doesn't play well with raw HTTP. Not too
mention it's got a bloated rendering and asset pipeline.

Anyway, my dayjob aside. This is the fix. We need to stop pretending
that the GAE makes any sense with it's ORM.
Merge branch 'develop' of https://github.com/EJEHardenberg/GreenUp into ios_networking
Deletion of Comments support

References #127

No update to the documentation yet, but the deletion is tested for
comments and working. Made sure to delete referenced pins from the
comment side. This seems to work correctly from the comment side unlike
when trying to delete pins.
Updated API Documentation

References #127

Placed details on delete errors for pins and comments into error
section.
Merge branch 'comment-deletion' into feature/type-clarification
Merge branch 'comment-deletion' into feature/type-clarification
Updated Readme a little

Removed non-working developers from list. Added list of all contributors
via command line fu
Merge branch 'feature/type-clarification' of github.com:EJEHardenberg/GreenUp into feature/type-clarification
Merge remote-tracking branch 'origin/feature/type-clarification' into ios_networking
premature merge with api verisoversion 3 as found in feature/type-clairification, updated pin and message types to match new API