Fixing missed call notifications for FBE

+ Our new components for creating missed call notifications are not
marked as encryption aware so Telecom was always creating the missed
call notification.
+ This CL marks the appropriate components as encryption aware so
Telecom can check to see if we support putting up the notification.
+ Updated logic so missed call notifications only have 'callback' and
'message' actions when not locked.
+ Misc FBE cleanup
  + Since the call log is not available when on the File
    based encryption lock screen, dismissed notifications will not
    attempt to mark the calls as read; attempting do so causes
    exceptions.
  + Updated AOSP Dialer to ensure that we don't store data in device
    encrypted storage by default. This storage location is always
    available, regardless of whether we're in the FBE locked state
    or not. None of our preferences/databases need to be available in
    this state, so this change causes the Dialer to store data in
    credential encrypted storage by default. This storage location is
    only available when the device is unlocked.
  + Updated AOSP Dialer so it doesn't use device encrypted storage by
    default. This is because we currently don't want any of the
    preferences/databases stored by the Dialer to be available when
    FBE locked.
  + Updated AOSP Dialer so specific components must mark themselves as
    encryption aware, rather than having everything aware because the
    application is marked as such.

Bug: 27455726
Change-Id: Ib5d28267116ec007bf9beb57862796235460ddf5