[Android] Use ant and xwalk_core_library for make_apk 

Previously, we are copying the python script from gyp
and reproduce the steps gyp generated to build
xwalk_app_template_apk to make apk.

It's hard to maintain and now xwalk_core_library is
mature enough to be used as Android Library Project.

This commit uses ant and xwalk_core_library to make
apk to replace previous approach.
```
The changes including:
1. The app packaging tool structure:
 a. Assets, jars and template code are now put in
    "template", jars includes xwalk_runtime_java
    and xwalk_app_runtime_java.
 b. xwalk_core_library will be put in root folder of
    packaging tool.
 c. Scripts used by gyp generated commands are removed.
2. When make apk:
 a. Embedded Mode:
  1) Copy template to app folder named according to
     input app name.
  2) Copy xwalk_core_library into app folder.
  3) Move arch folders under "app/xwalk_core_library/libs/"
     to "app/native_libs/<arch>"
  4) For each target arch:
   4.1) Run "android update lib-project" for app/xwalk_core_library.
   4.2) Run "android update project" for app.
   4.3) Remove all subfolder in "app/xwalk_core_library/libs",
        to make sure it will only contains one arch folder after 4.4).
   4.4) Move back the needed native library for target arch back.
        it's actually partly reverting step 3).
   4.5) Write down input keystore options to ant.properties.
   4.6) Run "ant release" in app.
   4.7) Copy and rename the built apk out to root folder of
        packaging tool.
 b. Shared Mode:
   1) Copy template to app folder named according to
      input app name.
   2) Remove xwalk_runtime_java.jar in "app/libs".
   3) Run "android update project" for app
   4) Write down input keystore options to ant.properties.
   5) Run "ant release in app.
   6) Copy and rename the built apk out to root folder of packaging
      tool.
```
BUG=https://crosswalk-project.org/jira/browse/XWALK-2128
This function still looks confusing to me, even if I ignore the parts related to `print_each_line_after`. I tried testing it like this:

```python
# my_test.py
import subprocess
s = subprocess.Popen(['python', 'get_input.py', stdout=subprocess.PIPE, stdin=subprocess.PIPE)
while True:
  if s.poll() is not None:
    break
  print s.stdout.readline()

# get_input.py
print 'some output'
print 'more output'
value = raw_input('Enter something: ')
print value
```

And it kept looping forever without printing anything. If I replace the `raw_input()` call in `get_input.py` with a call to `getpass.getpass()`, I get the "Enter something" prompt regardless of what I do to `stdout` or `stdin` in `subprocess.Popen()` or whether I `print s.stdout.readline()`.

I'm not sure how Ant's prompts work, but it seems to be that it could be used for both regular input a la `raw_input()` as well as for password prompts, which behave slightly different. Don't we risk getting stuck in a loop?