[Android] Refine the help information of packaging tool.

Group the options according their usage.

BUG=https://crosswalk-project.org/jira/browse/XWALK-666
[Extensions] Fix Android build
Merge pull request #1344 from cmarcelo/fix-android

[Extensions] Fix Android build
Fix the touch area and indicator size after rotation change
Merge pull request #1345 from kenchris/fixtouch

Fix the touch area and indicator size after rotation change
Fix more warnings for Tizen

Initialization order complaints from G++ 4.5.
Merge pull request #1348 from cmarcelo/fix-tizen-warnings-2

Fix more warnings for Tizen
Bump version to 3.32.56.0
Merge pull request #1324 from junmin-zhu/refine

[Android] Refine the help information of packaging tool.
[Tizen] Add CAP_MAC_ADMIN to XWalk binary.

XWalk on Tizen must be able to change its smack label.
For doing that it needs the CAP_MAC_ADMIN capability to be set to
its binary.

We do that because XWalk uses the same binary to spawn all of its
processes: the BrowserProcess (BP, the Runtime), the RenderProcess (RP)
and the ExtensionProcess (EP). For instance, after being forked,
RP will need to change its smack label to xwalk_renderer in order
to lower that process' privilegies. On the other hand, EP will change
its smack label to the web app id.

After doing that both EP and RP will drop their CAP_MAC_ADMIN
capabilities.
[Extensions][Tizen] Pass app_id to ExtensionProcess.

Add a new tizen-specific switch so we can pass the WebApp id
to the extension process. This process, in turn, we will use this
id as its SMACK label on Tizen.
[Extensions][Tizen] Change Crosswalk Processes SMACK label.

In order to keep its privileges to a bare minimum, the
Crosswalk processes (BP, RP, EP) need to:

1- BrowserProcess should use "xwalk" label;
2- ExtensionProcess should change its SMACK label from "xwalk" to its web app id;
3- RenderProcess should change its SMACK label from "xwalk" to "xwalk_renderer"
4- All processes but the BrowserProcess should drop their CAP_MAC_ADMIN capability ASAP.

The first step is accomplished by giving the "xwalk" execution label (SMACK64EXEC) to Crosswalk
binary. Since all other process are forked from the same binary, they will all have
the same starting label. We should then change that label accordingly.
This will guarantee that both EP and RP not only run with a different SMACK label
from the runtime (xwalk) but it will also them run with a label that provides access to all
the capabilities needed by their corresponding web app.

The RenderProcess, on the other hand, needs an even more restricted label
due to its own sandboxed nature. Its SMACK rules file (/etc/smack/accesses.d/xwalk_rp.rule)
will only add what is needed to communicate with other processes (EP and BP) and nothing
else.

Other SMACK rules files are added so we enable the BP and EP to talk
to each other (and to RP, of course) (/etc/smack/accesses.d/xwalk_ep.rule).
For last but not least, this commit also adds the needed rules to get BP working again
(/etc/smack/accesses.d/xwalk.rule). These rules were gathered by debugging SMACK
with dmesg on Tizen 2.x, with kernel built with CONFIG_AUDIT=y.

The fourth step drops the capability that enables a process
to change its SMACK label or to execute other MAC related commands.
WIP: merge this properly