Update documentation of Android build options

Author: rdb

distribution/list-of-build-options.rst

@@ -126,9 +126,19 @@ android_version_code
    to show an arbitrary dot-separated version string to the user. Every time you
    upload a new release to the Play Console, this number must be increased.
 
+android_app_category
+   How the app is categorized, should be one of "accessibility", "audio",
+   "game", "image", "maps", "news", "productivity", "social", or "video".
+
+android_debuggable
+   A boolean indicating whether the app can be debugged. It is recommended to
+   set this to True during testing.
+
 android_min_sdk_version
    Overrides the lowest version of Android that the game will still operate on.
-   The default is the minimum version of Android that Panda3D supports (19).
+   The default is the minimum version of Android that Panda3D supports (21), it
+   could make sense to increase this if your app uses additional APIs that are
+   only available in newer versions.
 
 android_max_sdk_version
    Overrides the highest version of Android that the game will still operate on.
@@ -148,6 +158,17 @@ android_abis
    During testing, to shorten build times, it may be useful to set it to just
    one architecture.
 
+android_manifest_file
+   Path to an AndroidManifest.xml file that is included instead of the one
+   generated by build_apps.  This can be used to further customize the app
+   beyond what these settings permit. The settings in the file will override
+   those specified in the build options. However, it is easy to get something
+   wrong and break the app. Very little checking is performed to determine
+   whether the provided file is consistent with the supplied build options and
+   will result in a working build. It is recommended to first use build_apps to
+   generate a working AndroidManifest.xml and then modify it further to suit
+   your needs.
+
 bdist_apps
 ----------