[webapi][XWALK-1195] Add 44 tests for mediaRenderer

- Add 44 tests for mediaRenderer
- Failure analysis: MediaRenderer does not support

Impacted tests(approved): new 44, update 0, delete 0
Unit test platform: [Tizen IVI]
Unit test result summary: pass 0, fail 4, block 40
[usecase-webapi] Make usecase of Workers better.

- Modify the button name 'Start' to 'Calculation'.

Impacted tests(approved): New 0, Update 1, Delete 0
Unit test platform: [Tizen IVI]
Unit test result summary: Pass 1, Fail 0, Block 0
[webapi][XWALK-522] Optimize the test cases for promises

Impacted tests(approved): new 1, update 3, delete 0
Unit test platform: [Android]
Unit test result summary: pass 4, fail 0, block 0
[usecase-webapi] Improve vibration for misc usecase w3c

- Use vibration "on/off" button and button style "center"

Impacted TCs num(designed): New 0, Update 1, Delete 0
Unit test Platform: Tizen M0
Tizen test result summary: Pass 1, Fail 0, Blocked 0
[usecase-webapi] Disable forward button and show history state
Fix incorrect urls in WebSocket tests.

Replaced location.hostname with "127.0.0.1", as it was empty,
what lead to invalid urls.
extract some common steps into libiary
[usecase-webapi] Improve SIMD usecase

- Adjust the case with screen view

Impacted TCs num(approved): New 0, Update 1, Delete 0
Unit test Platform: [Andriod]
Test result summary: Pass 1, Fail 0, Blocked 0
[usecase-webapi] Improve the w3c usecase for HrtimeTizen
[usecase-webapi] Improve the usecase for HrtimrAndroid

- Change button to "Waiting" when play, and disable the button. Change back when play end.
- Put the result info "The time of video playing is" below the play button.
- Remove "Android" and "Tizen" in test purpose

Impacted tests(designed|approved): new 0, update 1, delete 0
Unit test platform: [Android]
Unit test result summary: pass 1, fail 0, block 0
Update pack script and BDD test framework.
[webapi][XWALK-432] Add 58 Tcs for nfc

- Failure analysis: nfc does not support

Impacted tests(approved/designed): new 58, update 0, delete 0
Unit test platform: [Tizen IVI]
Unit test result summary: pass 0, fail 12, block 0
[wrt] Add 3 apk source for wrt-rtcoremanu-android-tests
[wrt] Add apk source for wrt-securitymanu-android-tests
[wrt] Update pack.sh for wrt-webfeaturesmanu-android-tests
[wrt]update manual/auto test suite
[wrt] Update apksource and script for wrt-packagemgtmanu-android-tests
[wrt] Update pack.sh for wrt-manifestspecificmanu-android-tests
[wrt] Update appsource and pack.sh for wrt-extensionmanu-android-tests
Fix tests incompatible with latest WebSocket spec.

[Issue#]   265
[Problem]  Failing TCT tests.
[Cause]    The tests call WebSocket.close() and expect to get an
           onmessage event after the call and before the
           connection is closed. This can not happen according to
           the WebSocket spec.

           There are two important points:

           The first point is what WebSocket.close() is supposed
           to do:
           http://www.w3.org/TR/websockets/#dom-websocket-close

           3. -> Otherwise section applies in all tests:
           "Set the readyState attribute's value to CLOSING"

           The other point is what happens when readyState is
           not OPEN:

           http://www.w3.org/TR/websockets/#feedback-from-the-protocol

           "When a WebSocket message has been received ... follow
            these steps:

           1. If the readyState attribute's value is not OPEN, then
              abort these steps."

           Chromium aborts at step one, preventing any further
           onmessage events. The event handler would be called in
           step 5.

           All these tests call WebSocket.close() before the onmessage
           event is received, preventing the event to be delivered.

[Solution] Move the call to WebSocket.close() to the end of the
           onmessage event handler.

Change-Id: I068c008de8972c01a1d815c16ad16f9fe21a5ae0