Bug 1042939 - Alarms, periodic sync, notifications refactor r=millermedeiros

_Note_: This is a work in progress!

### Summary of changes

There are a few different pieces of functionality affected.

#### Periodic sync

1. When the calendar starts, if periodic sync is enabled, we should write an alarm to mozAlarms to wake us up for periodic sync.
2. If the user changes the periodic sync interval, we should revoke any previous periodic sync alarms and issue a new one at the modified interval.
3. When we get woken up by a periodic sync alarm, sync and then issue a new alarm.

#### Notifications

1. When we receive an event reminder from the alarms api, send a notification via the notifications api about the reminder. When that notification gets clicked, navigate to the alarm url.

### What's coming!!

1. Fix for calendar alarm spam.
2.  Don't start periodic sync until we have a calendar that needs a real sync operation.
3. Calendar opens and stays open after using an alarm.
you already called `Date.now()` a few lines above.. Maybe do:

```js
var begins = Calendar.Calc.dateFromTransport(busytime.start);
var distance = app.dateFormat.fromNow(begins);
var now = Date.now();

debug('Event begins:', begins);
debug('Now:', now);
debug('Distance:', distance);

var type = begins > now ? 'alarm-start-notice' : 'alarm-started-notice';
```

`Date.now()` is usually better since it avoids creating a new `Date` object.. (cached value for brevity)