Adds survey availability notices, optimizes survey list and triggers, fixes bug with Realm data

[sophiabersani]

This PR is a series of related tasks related to the survey list and triggers.

Realm version had to be updated to fix a common bug. Be sure to run npm install after merging this branch.

Stories:
https://www.pivotaltracker.com/story/show/120683843
https://www.pivotaltracker.com/story/show/121071009
https://www.pivotaltracker.com/story/show/121131787

Features:

• Adds a notice for triggered forms in the survey list.

Changes:

• Refactored Trigger detection to support checks on individual Surveys.
• Adds an instant trigger check on accepting a survey.
• Omits push notifications for instant triggers to avoid spam when accepting forms.

Bug fixes:

• Fixes a styling issue that caused survey list items to hide behind the filter menu.
• Updates Realm version to fix a crash happening on new schema versions and migration.

[dan-nyanko]

@gbersani ping

[dan-nyanko]

Also, this is likely going to need updated to work on Android. So I'd prefer this to happen after #100

[sophiabersani]

Sounds good.
I've already had to do some heavy conflict resolution on my map-view branch to get it on par with #100, this one shouldn't be as bad.

[dan-nyanko]

Are we checking for 'none' somewhere that we are defaulting to this value? Perhaps a preference thing, but why not null?

[dan-nyanko]

The reason I don't like defaulting to a 'none' string, is that its a truthy value and could lead to a potential bug.

[sophiabersani]

From what I found Realm can perform automatic migrations, having the default set can prevent a few crashes when updating objects when calling these new properties.

There's no easy way to check if a value is null with a query, as it forces strict type casting.

[dan-nyanko]

Seems like its been added: realm 162.