TIMOB-8838: <BlackBerry: Implement UI.TableView>

Reviewers: Alex, Davic C.

Change Log:
- implemented BB support of tableView controller
- implemented dictionary JV type parser
- fixed issues which came from some merge for textField

TestCases
- build tibb
- build tibtest
- instance java script tableView object with certain properties
  implemented here
- make run tibbtest project make sure properties/events are working
- run docgen.py script
- make sure documentation includes updates
Addressed comments
TIMOB-9204: <BlackBerry: Bring API doc up to date>

Reviewers: D. Lifshitz, JP

Updated API docs for imageView, textField and activityIndicator UI
controllers
Merge branch 'TIMOB-8944_01' into TIMOB-8944_WIP_04
TIMOB-8944: BlackBerry: BlackBerry: Connect drillbit to BB simulator or device

[Issues Fixed]
TIMOB-8944: BlackBerry: BlackBerry: Connect drillbit to BB simulator or device

[Changes]
blackberry.js
- function run
  - removed useless blackberrySimulatorProcess
  - remember readLineCb
- function launchTestHarness
  - when finished starting up the test harness, capture the logs and check the exit code
- added stub function handleCompleteBlackBerryEvent

blackberryndk.py
- added functions printExitCode, _isAppRunning, _printAppLog, appLog

devicemanagement.py
- added commands and functions printExitCode, appLog

[Tests]
Test 1: Run drillbit
1) Run scons to build the mobile sdk
2) Run the following command:
drillbit\drillbit.py --platforms=blackberry
3) Click "run tests"
4) Verify the test_harness app is built, deployed, and run
5) Close the app on the simulator
6) Verify the logs are printed
Note: The test will not finish because the app was closed manually (not what should happen) and the framework doesn't yet output the Ti logging.
If you want to see the test fail when the app crashes, put a return -1; in tibbapp/main.cpp.
TIMOB-8990: Ti functions don't work in event callbacks
Reviewers: David L, Alex

Description:
This patch fixes the problem of JS functions not calling back to the runtime. This patch calls "setVisible(false)" in the "clicked" event on the button object. In previous verions, this wouldn't work because it was never passed to the runtime.

Change Log:
- created a callback for Cascades message loop
- changed V8 scope so context doesn't go out of scope before events are handled
- application exits when a JS exception occurs

Test Cases:
- build tibb
- build tibbtest
- run tibbtest in simulator or device
- push the button - it should disappear

Note:
This patch addresses issues:
https://jira.appcelerator.org/browse/TIMOB-8990
https://jira.appcelerator.org/browse/TIMOB-9203
Addressed comments.
Addressed comments
Merge branch 'blackberry' into TIMOB-8944_02
fix copy & paste typo
Address comment
Addressed comments.
Merge pull request #64 from dlifshitz-maca/TIMOB-8944_02

TIMOB-8944: BlackBerry: BlackBerry: Connect drillbit to BB simulator or device
Added comment for activity indicator
Merge branch 'blackberry' into apidoc
- updated activity indicator apidoc
- add todo for toggle Button object
Merge pull request #63 from Harutyun/apidoc

TIMOB-9204: <BlackBerry: Bring API doc up to date>
Addressed comment
TIMOB-8921: Blackberry: Add functionality to specify ip address (device/simulator) and (optionally) password ver4

Reviewers: JP, David L

ChangeLog
- Remove ip validation to support hostnames
- Update --password to --device_password

Tests
 1) Create project using project.py script
 2) Run builder.py by providing ip address and password (optionally, if set in simulator/device)
 3) Make sure application successfully built and installed on simulator/device
 4) Make sure launch failed if password set, but doesn't provided
 5) Make sure launch succeeded if password not set, but provided
 6) Make sure ip validation returns error on non-valid ip address

Conflicts:

	support/blackberry/builder.py
TIMOB-8921: Blackberry: Add functionality to specify ip address (device/simulator) and (optionally) password ver5

Reviewers: JP, David L

ChangeLog
- Minor improvements

[Tests]
 1) Create project using project.py script
 2) Run builder.py by providing ip address and password (optionally, if set in simulator/device)
 3) Make sure application successfully built and installed on simulator/device
 4) Make sure launch failed if password set, but doesn't provided
 5) Make sure launch succeeded if password not set, but provided
 6) Make sure ip validation returns error on non-valid ip address

Conflicts:

	support/blackberry/builder.py