RC : Allow user selectable StatusBar FontSize

PS 1: Combined the the FW side, this will allow the user to select
a custom font-size for text used on the StatusBar.
Note that I put this in 'Signal' area for now, but really needs to be on the
main preference screen as a sub-category of StatusBar (or in Gen UI?)
I didn't want to try and put in main area as no other preferences are set
directly there (all lead to other fragments).  But putting it in Signal
is misleading, as it effects other areas.  Putting in GenUI might be best,
but that area is already way too crowded.

ps 2:  Rebased and moved setting to GenUI.
ps 3: Fixed persistence of setting
Change-Id: Iadcecf66c23d98fca5557047eedf711e47b042dd
Signed-off-by: Zaphod <mwilson@acesappraisal.com>

Conflicts:

	res/values/arrays.xml
	res/values/strings.xml
	res/xml/prefs_ui.xml
	src/com/aokp/romcontrol/fragments/StatusBarSignal.java
	src/com/aokp/romcontrol/fragments/UserInterface.java
FW Ribbons Swipe ribbons seperated && logic adjust for navbar

If you have an enabled navbar weither by default or user seleted
the bottom ribbon has not been available. If the user manually
hides the navbar I will allwo them to use the bottom ribbon.
They can also long press the hidden navbar handle to get the
bottom ribbon.

This also makes the left right and bottom their own ribbons.

Change-Id: Icba9c4ec510149bef74382a3bf59fd79b3ef87c4

Conflicts:

	core/java/android/provider/Settings.java
	core/java/com/android/internal/util/aokp/AokpRibbonHelper.java
	packages/SystemUI/src/com/android/systemui/aokp/AokpSwipeRibbon.java

Signed-off-by: igio90 <giovanni.rocca.90@gmail.com>
FW: settings: arrayList API rework

There is nothing wrong with the current implementation
it just requires some implicit knowledge about the internals
which should not be used for an API added at such a central
location
To reset the value back to "" you must know that setString
musst be used instead of providing just an empty list which
would be a more "logical" approach
With this the client code would also become easier cause
the check for size()>0 would not be longer required
e.g. in RibbonTargets
I would also suggest to change getArrayList so that it
returns an empty list for the case that the value is ""
instead of an list with size 1 and the single item ""
Allthough this would be a change in the API it would
make the API sync with the putArrayList and would also
be the more "logical" return value for this case
I think I have checked all current uses of getArrayList
and as far as I can see that change would have no impact
on the existing code. But please correct me if I am
wrong with this.

Signed-off-by: igio90 <giovanni.rocca.90@gmail.com>