Fixed error handling when deploying

• Fixes an error handling issue when deploying a new version of an already-existing connector
• Connectors that are being updated as part of the deploy command are no longer stopped before the update, and resumed after

Proper deploy() error handling

When using the deploy command on a whole folder, raise an error and stop the deployment if a file could not be parsed, instead of logging (info-level) and continuing with the deployment. This is a potential breaking change if non-config files are placed in the folder containing the configuration files.
Add some unit tests on the cmd package.

Custom HTTP headers support

Support the addition of custom HTTP headers

Go modules

Switch from dep vendoring to go modules

2.1.0

Add basic authentication

2.0.2

support mutual authentication with certificate

2.0.1

• errors from deployment() was not aggregated
• add parallelism config
• increase timeout, waitTime and retry count
• wrap some error for easier debug
• don't use Error() != nil as it is not reseted on retry

2.0.1-RC2

Deploy multiple (#32)

Multiple deployment

Change are a bit small for a new major version but for simplicity we broke the API

• add multiple deployment feature
• rework lib to expose HighLevel client
• in cli --file/-f parameter become --path/-p

fix error handling in REST client

Some random fixes on REST client (#31)

- rm useless setRestMode
- rm fall back to string error parser because to complicated
- define expected status code where error is definitive for each calls
- actually return an error when such such situation occurs
- retry all 409