core: Remove QCOM BoostFramework and ActivityTrigger

core: Remove QCOM BoostFramework and ActivityTrigger

These rely on a bunch of proprietary libs that not
all devices support. CM has its own boosting solution
anyway, rendering these additions unnecessary.

One small, but important change has been omitted from the revert,
that is the addition of ro.sys.fw.bg_apps_limit in the file
services/core/java/com/android/server/am/ProcessList.java.

This reverts the following commits:
c35293c3be2b5a0eaf1986b6772040a19f2d828a Framework for LaunchBoost v2 and Frequency aggr during launch.
91338fb35fcc9a155345d284bc24fad86f4d33a8 frameworks: Add custom boost for scroll/fling
911884e18f8e7ec76bf9db5ea9a91e6f0d65ba6b Perf: Adding hooks for IO prefetcher into framework
f56206d659dd686db3f7bf3c2660609917e9777d BoostFramework to enhance performance during critical scenarios
d841ef6271723021a663243ff34284a33a15cebf add network related API into ActivityTrigger
2f1b28122493a80448f3af499d660a5b7cbaa879 Set animation scale values for specific activity.
4ea9a4ec7fac2bf280a72149277b74a53d222cbc frameworks/base: activity pause/stop event triggers
015851c69698ff9558f3f0c7208a06083728cdad frameworks/base: Tap process start event to trigger perf lib.
e14378bf325f07b9133156ff82a18bb15f3f3716 frameworks/base: Add support for low resolution rendering
4d9ec1350434aa71540801e7fa42cee82c06beed ActivityTrigger: New class to invoke when activity starts/resumes

Change-Id: Iafdc3866c39d4e0d51ca2d40931ea9a5baba7de5