#45 add timeout to train job

[ibm-peach-fish]

closes #45

[kellyaa]

Looks like a good approach. Two things:

• Can you add a unit test that tests setting the timeout and makes sure the job ends at the timeout? We'll probably also want to make sure that when we call get_info() on the RayTrainModelFuture after the job times out, that is returns an expected state.
• Run tox -e fmt on your dev env and let it modify your file to make the linter happy before doing to next commit!

[ibm-peach-fish]

thanks for the quick review @kellyaa

ack on the unit test, i'll do that this morning

i did do the tox -e fmt and tox -e lint before i committed, then didn't go back to check it worked. I will next time and tinker with it if it still gives me bad noise

[ibm-peach-fish]

@kellyaa this is ready for (re)review

[kellyaa]

Looks great!