Add ability to pass crystal --error-trace to lucky watch task.

[jwoertink]

Purpose

Fixes #947

Description

Allows you to pass crystal's --error-trace flag in to lucky watch command. When you run lucky dev, and encounter a compiler error, you'll be given the full trace each time.

Checklist

• - An issue already exists detailing the issue/or feature request that this PR fixes
• - All specs are formatted with crystal tool format spec src
• - Inline documentation has been added and/or updated
• - Lucky builds on docker with ./script/setup
• - All builds and specs pass on docker with ./script/test

[paulcsmith]

This looks good. My only thought here is that we should probqbly see if the Crystal team could add a SHOW_FULL_CRYSTAL_ERROR_TRACE ENV var that can be set to 1 or true so that it people can set it in their shell or before a command and not worry about it passing the flag. This can be helpful to any command line tool written in Crystal

[paulcsmith]

Added an issue to Crystal here: crystal-lang/crystal#8374

[jwoertink]

I've added a little todo note for us to revisit if that crystal issue ever becomes a thing. I think getting this merged in for now will be good just so people can take advantage of the full errors. I'll merge once these builds finish and pass.

[paulcsmith]

Agreed! Thanks @jwoertink

[bdtomlin]

@jwoertink, thanks for this. Super helpful!

[Napolskih]

@jwoertink not fixed!

[jwoertink]

@Napolskih You have to make sure that your lucky -v is on at least 1.0.0 or later. Since 1.1.0 is the latest as of right now, you should upgrade to that.

[Napolskih]

[jwoertink]

What version is listed in your shard.yml file?

[Napolskih]

Thanks I got it.

Lucky_jumpstart needs to be removed from the documentation or updated.