[TRI-644] On a Run retry add info to `context.run`

[matt-aitken]

When this button is pressed it retries the existing run.

Image source

In this case, we should add some metadata to context.run so you can identify that it is a rerun and potentially how many attempts have been made as well.

_{From SyncLinear.com | TRI-644}

[ericallam]

I think initially we should just add an isRetry boolean in the context.run object

[ericallam]

/bounty $100

[algora-pbc]

💎 $100 bounty created by ericallam
🙋 If you start working on this, comment /attempt #154 to notify everyone
👉 To claim this bounty, submit a pull request that includes the text /claim #154 somewhere in its body
📝 Before proceeding, please make sure you can receive payouts in your country
💵 Payment arrives in your account 2-5 days after the bounty is rewarded
💯 You keep 100% of the bounty award
🙏 Thank you for contributing to triggerdotdev/trigger.dev!

Attempt	Started	Solution
🟢 @akhill10	Jul 14, 2023	#177

[akhill10]

/attempt #154

New to this repo. Seems like a good issue to start contributing. I will take this up 😃

@ericallam If I understand it correctly, when it retries the existing run, it creates an eventLog ( EventRecord ) with the context same as existing run context. We just need to add an isRetry boolean to this context right?

[algora-pbc]

💡 @akhill10 submitted a pull request that claims the bounty. You can visit your org dashboard to reward.

[algora-pbc]

🎉🎈 @akhill10 has been awarded $100! 🎈🎊