sdk: Move to new button and keyboard brightness configs

For as strange as it may be, so far the visibility of the features depended
on the default value of config_{button,keyboard}BrightnessSettingDefaultFloat.
This was nonsense, because it would force everyone to overlay that default
with a value of 0.0, just to make the unsupported feature go away.

Change-Id: If605238bf30642db057b06b03224d9a8b4451f12

lineage/res/res/values/config.xml

@@ -248,9 +248,19 @@
          before setting power profiles on boot. -->
     <bool name="config_waitForMpctlOnBoot">false</bool>
 
-    <!-- Button and keyboard backlight -->
-    <bool name="config_deviceHasVariableButtonBrightness">false</bool>
+    <!-- Button backlight control. Possible values are:
+            0 - Not supported
+            1 - Supported, but only on/off mode
+            2 - Supported with variable brightness control
+    -->
+    <integer name="config_deviceSupportsButtonBrightnessControl">0</integer>
     <dimen name="config_buttonBrightnessSettingDefaultFloat">1.0</dimen>
+
+    <!-- Keyboard backlight control. Possible values are:
+            0 - Not supported
+            1 - Supported with variable brightness control
+    -->
+    <integer name="config_deviceSupportsKeyboardBrightnessControl">0</integer>
     <dimen name="config_keyboardBrightnessSettingDefaultFloat">1.0</dimen>
 
     <!-- Whether to cleanup fingerprints upon connection to the daemon and when

lineage/res/res/values/symbols.xml

@@ -172,7 +172,8 @@
     <java-symbol type="bool" name="config_haveNotch" />
 
     <!-- Button and keyboard backlight -->
-    <java-symbol type="bool" name="config_deviceHasVariableButtonBrightness" />
+    <java-symbol type="integer" name="config_deviceSupportsButtonBrightnessControl" />
+    <java-symbol type="integer" name="config_deviceSupportsKeyboardBrightnessControl" />
     <java-symbol type="dimen" name="config_buttonBrightnessSettingDefaultFloat" />
     <java-symbol type="dimen" name="config_keyboardBrightnessSettingDefaultFloat" />