[2/3] Keep InCallUI in memory

In lower end devices, startup of the InCallUI process can take
up to 10 seconds when the device is busy, which prevents the user
from taking the call. Keep the process in memory like previous
versions where they are a part of Phone.apk.

This converts InCallUI into a dummy apk with the persistent
attribute set to true and allows the activity from Dialer.apk,
which uses the com.android.incallui process to be loaded into the
persistent process.

NOTE: This issue even occurs from time to time on mako,
which is one of the devices I build FFFFUUUUUU for,
which is not normally considered as a lower end device.
So...I think it might be a good idea to add this feature
to FFFFUUUUUU. It won't bite anyway.

[2/3] InCallUI常驻内存

在低端设备上, 设备处于高占用状态时, InCallUI进程的
启动耗时甚至能达到10秒钟, 这导致用户无法接听电话.
将这个进程写入常驻内存, 像以前的版本中一样(该进程曾是
Phone.apk的一部分).

这条commit将InCallUI转换成一个拥有常驻进程的傀儡apk,
并使Dialer.apk中占用com.android.incallui进程
的活动变成一个常驻进程.

NOTE: 这个问题甚至偶尔在mako上都会出现, 而mako是
FFFFUUUUUU支持的设备之一, 并且通常不被认为是一个
低端设备.
因此我认为将这个特性加入FFFFUUUUUU没准是一个好主意.
反正至少没啥坏处.

Here, we set the sharedUserId so the dummy
InCallUI.apk can share the process.

这里我们设置一个sharedUserId, 从而让傀儡
InCallUI.apk可以共享进程.

[1/3] in platform_packages_apps_InCallUI
[3/3] in platform_build