NEW: Environment variable to disable CommonJS environement building

This patch allows user to disable the commonJS build phase by setting the system environement variable IGNORE_ENV_COMMONJS.

For instance `export IGNORE_ENV_COMMONJS=1`
New: new options for the command objj

This pull requests adds the following feature for the command objj:

- Option -h or --help to get the help of the command
- Option -I or --objj-include-paths to specify the frameworks to be used
- Possibility to pass several files to the command, for example objj AppController.j Test.j
New: Added option --parser/-p to the command objj

Previously it wasn't possible to specify a custom parser for the command objj. This is needed for xCodeCapp
Fixed: part of the code missing after the previous commit refs #f21dcb8265d78683f984aa70014e1fb91a191ae7
Fixed: change option -p in objj by bash concept --
Fixed: fixed issue with press, capp and nib2cib with the new command objj
Test: updated test ToolTest.j. Added tests for capp_lint and objj
Test: removed test for capp_lint
Revert "Test: removed test for capp_lint"

This reverts commit 2bf012100a04eb67714486a1dcffd67d1c51f519.
Test: removed test for capp_lint
Fixed: added options -m for objj. This option allows you to make objj on several files
Merge pull request #2242 from primalmotion/disable-flag-for-commonjs-environement

NEW: Environment variable to disable CommonJS environement building
FIXED: Some APIs in CPComboBox were broken

Previously, when setting font, alignement, intercellSpacing or itemHeight, CPComboBox was assuming the listDelegate was already created.
This patch stores the values in CPComboBox if the listDelegate is not ready, and apply them once it is.
STYLE: Make previous patch cleaner
Fixed: when using the option -m, objj doesn't process every files in a error is raised, now it does
FIXED: Open the popup list as a child window in CPComboBox
New: xCodeCapp 3.2, command objj on each processing files or on the entire project

This pull requests adds a nice feature to xCodeCapp, now each time a fill is processing, xCodeCapp will launch the command objj to check the compilation issues. If it finds something, it will show them up on the classic error panel. This basically show import warnings, warnings you don't catch with your browser but only during the build of the application.
Objj is only launched if no errors was found after the first parsing (the parser which translate a file to objective-c).

This feature can be disabled on the preferences panel.

The menu has a new menu item "Check Compilation Issues". This action will launch objj on each files of the project and shows warnings and errors found.

The command objj will take automatically the OBJJ_INCLUDE_PATH in the index.html or index-debug.html. This options can be disabled in the preferences panel as well.

This PR only works with the PR #2248
Fixed: removed unused constant
Merge pull request #2248 from Dogild/OBJJEnhancement

New: new options for the command objj
Merge branch 'xCodeCapp3.2' of https://github.com/Dogild/cappuccino

Conflicts:
	Tools/XcodeCapp/XcodeCapp/ProcessSourceOperation.m