Implement complete set of HTTP methods

[Bravo555]

As seen on wikipedia page about REST, there are some fancy HTTP methods we're not using. Implementing them would decrease the quantity of needed endpoints and make API more convenient and natural to use.

[Bravo555]

Before actually implementing, it would be nice to have complete list of needed changes.
Summoning @JJendryka

• /accept_with_token/:id/:token and /reject_with_token/:id/:token are rather verbose. They could be replaced with PATCH and DELETE to /quotes/:id.
• Since /daily, as @JJendryka said, makes a new entry in a daily collection (that's why it's POST), it would be nice to actually have this collection accessible (make /dailies) and submit new daily via /dailies/new.

[Bravo555]

More data about API design. What HTTP response status codes to use.

[Bravo555]

🔒 - With token authorization

/quotes

• /quotes (only accepted quotes)
  • GET Get all the quotes. Implement paging and sorting in the future.
  • POST Submit new quote.
• /quotes/:id
  • GET Get the quote.
  • PATCH Accept the quote or change its text, annotation, date. 🔒
  • DELETE Delete the quote (or reject it). 🔒
• /random -> /quotes/random
  • GET - Get random quote.
• /daily -> /quotes/daily
  • GET Get today's quote.
  • POST Make a new daily. 🔒
• /submissions -> /quotes/submissions
  /quote/submissions is a view of quote which shows submitted and not yet accepted quotes. All endpoints of /quotes apply here.
• /submissions - only not accepted quotes are here.
• /submit -> POST /quotes
• /accept -> PATCH /quotes/:id

As accept|reject_with_token endpoints are now used by email notification system, they should not be removed until we make email system use them.

All updated endpoints in 1.0.0 will be prepended with /v1 in the URL.