Added `stackTraceLimit` configuration, fixes #96.

The new option `stackTraceLimit`, like the corresponding option in
Chrome, allows us to specify how many stack frames we want when
stopped at a breakpoint. It can be set as high as you like.
Negative numbers will cause an error.

The default number of frames is set to 50 to prevent possible
performance issues; if you wish to capture all frames, no matter the
consequences, set this option to a high number, like `99999`.
Updated AUTHORS.
gjslint: removed workaround for linter bug

Removed workaround for the bug where the linter incorrectly reported errors
for members with no documentation. The issue is no longer present as of version
2.3.12.
package.json: changed the next version to 0.6.0
git-changelog: detect version from package.json
ChangeLog: updated for version v0.6.0
started work on v0.6.1