Updated the installation instructions to include couchdb-lucene
Multiple recipients in messaging

Allow a user to send a message to multiple recipients.

Issue: #333
Added option to select everyone at a facility

Issue: #427
Fix a bug where it is possible to send a message twice by double clicking the submit button
WIP #333
Merge branch 'feature/333' of github.com:medic/kujua-lite into feature/333

Conflicts:
	lib/data_records.js
Fixed html on outgoing message record display for multiple messages #333

Displaying message details stacked in the expanded rather than collapsed
into one message.  It's overly repetitive, UI pass to follow once we get
feedback, for now just focusing on functionality.

If more than two recipients then display "x recipients" otherwise join
the recipients with a comma and potential ellipses.

Added optional messages parameter to @contact template helper.

Added pending/sent icons to outgoing message rows so you know the status
of messages at a glance.

Added message timestamp to each message detail.

Added `facility` property to message.

So bulk-sms/multi-recipient message generates a tasks property structure
shown below.  Considering adding the entire facility document to the
message object since that will be needed for display.

```
[
   {
       "messages": [
           {
               "sent_by": "admin",
               "to": "+525550761785",
               "facility": "d049925d-72da-063b-24ff65327348e7be",
               "message": "foo bar",
               "uuid": "f5daf0c1-61b7-1df5-79bec3aff4a9e750"
           }
       ],
       "state": "pending"
   },
   {
       "messages": [
           {
               "sent_by": "admin",
               "to": "+254771559999",
               "facility": "d049925d-72da-063b-24ff65327348420e",
               "message": "foo bar",
               "uuid": "f5daf0c1-61b7-1df5-79bec3aff4a9f553"
           }
       ],
       "state": "pending"
   }
]
```

Only assigning first recipient facility to record.related_entities since
that property determines who can view the record. Not sure how to handle
the record's permissions with a mult-recipient case yet.  Mabye reduce
the recipients list into the most common parent.  related_entities on
the record probably needs to be converted into a list eventually so a
record can belong to more than one district?  But this is a major
architecural change and would require changes throughout the code base.
Merge branch 'develop' into feature/333
added facility property to message object #333

Renamed checkMessageDoc to createMessageDoc and simplified a bit. Since
facility is getting passed in through the select2 form in
`mapContactResult` now we don't need to make a separate request to fetch
the facility.
Merge branch 'feature/333' into develop

Conflicts:
	lib/data_records.js
removed tests for `lib.data_records.checkMessageDoc` function changed.

Tests pass now.  Function was simplified renamed to `createMessageDoc`
in earlier commit, tests refactor would add little value.

TODO find weaknesses in other parts of the new bulk messaging code and
add tests around that.