The Get endpoint already exists on the service, so only the List endpoint
needed to be added there.

BACK-2554

Through discussions it was confirmed that Repeat is not universal to all
alerts. So it's lifted out of the Base alert and re-inserted into those alerts
where it should be present (namely Low and High alerts only).

BACK-2554

These activity properties will track the times at which alerts were sent,
resolved, or acknowledged.

BACK-2554

This endpoint will be used by upcoming changes to the auth client to allow
care partner backend processes to retrieve device tokens in order to send
mobile device push notifications.

BACK-2554

This functionality will be used by care partner processes to retrieve device
tokens in order to send mobile device push notifications in response to care
partner alerts being triggered.

BACK-2554

This was missed when moving device tokens from the data service to the auth
service in commit a0f5a84.

BACK-2554

Basic steps are taken to allow for other push notification services to be
easily added in the future.

BACK-2554

So that sarama log messages better follow our standards, and will be emitted
as JSON when log.Logger is configured for that.

Before this change, the sarama logs were printed in plain-text without any of
the benefits of the platform log.Logger.

BACK-2554

The existing FaultTolerantConsumer isn't used because it's retry semantics are
hard-wired and aren't compatible with what care partner alerting's needs.

Note: A proper implementation of AlertsEventsConsumer to consume events is yet
to be written. It will follow shortly.

BACK-2554

The upload id is necessary to ensure that only the proper device data uploads
are evaluated for care partner alert conditions.

BACK-2554

If the necessary configuration isn't found, then push notifications will
instead be logged.

BACK-2554

These methods return Note objects that can be sent as push notifications.

NotLooping evaluation will be handled in a later commit.

BACK-2554

It uses the new asyncevents from go-common, as alerts processing requires
different retry semantics than the existing solution.

The Pusher interface is moved out of data/service into data/events to avoid a
circular dependency.

BACK-2554

No longer needed

BACK-2559