Wear test: API add an "invite" resource

1. ��First download the API code [Post Registation Details.API SRC] and read the README_queue.md to understand how the queing works.
2. ��Next register a new tester [Post Registration Details.Demo Client URL] with a valid email that you have access to, to understand how the email works (see services/workers/mailer.js and woker.js) when you register a new user (choose tester) you should get an email generated by these two files.
3. ��Feel free to create as many testers as you like, but they must be unique email address. �� The + trick doesn't work so you will actually need to have those emails, However you can go into the admin tools and add the + trick (http://notfaq.wordpress.com/2006/07/20/plus-sign-in-email-addresses/) to the emails after they have been created��
4. ��Next you should login as cs_brand [Post Registration Details.Logins] and create a wear test with at least the title and Product Test Overview(wearTestOverview). ��The test name should contain this challenge 2715, your cloudspokes username, and a number to distinguish it (1,2,3..)
5. ��You may create as many wear test as you like ��and use [Post Registration Details.Wear test Query] to get the ids��
6. ��Download the API and look at the [Post Registration Details.Env Vars] and you are ready to go.
8. You shouldn't use the webclient to fire your solution. �� Just create an api call, the LEMUR endpoint has the api_key turned off for your convince.

1. Create a api resource called invite takes the following values in the body (weartestid, testerid, userid, Email Template Name). The testerid is the user.id of the tester and the userid is the id of the user who is making the call (use cs_brand for this)
2. The endpoint should be able to take more than one testerid (bulk operation)
3. This service should first validate the testerid is not already invited, or on-team
4. This service should secondly check the weartest is ready ( now just check that it has the property wearTestOverview ) but organize your code so we can add more logic here like making sure the dates are in the future. Create a placeholder for this logic.
5. This service should thirdly update the weartest particpant subdoc status to 'invited' if they are already in the particpant subdoc or add them.
6. This service should fourthly send an email to the tester using the EMAIL_TEMPLATE_INVITE_2715 (or you can create your own from the admin crude tool | Content)
7. This service should fifthly create an useful log message that can be used for debugging later.
8. Please submit very detailed documentation of your solution so we can use it for our next challenge
9. Please include a video of your solution and a code walk-through (You may provide text narration in your video if you are not comfortable with your spoke English )
10. You should provide a mechanism to shut off the mail portion of this service via an .env var. For example SEND_INVITES=false
11. Provide a POSTMAN or curl example to show your api call