exclude managed/hidden-body classes from refresh results
now can work with two distinct connections Partner and Tooling as required
triggers also can have hidden/managed body, so need to exclude those
started adding support for deployment using Metatada API

Tooling API can't handle mixed create/update packages
switched from '--param value'  to '--param=value' config parameters format
clean-up values enclosed in quotes

+ basic Config class unit tests
updated README regarding the current state of Force.com Tooling API