[TRI-1135] Add job management API endpoints

[ericallam]

We need to flesh out our API to allow you to manage jobs and runs:

• Get a list of runs for a specific job (with filtering for status, environment, etc.)
• Get task data for a specific run
• Cancel a run
• Retry a run
• Resume a run
• Test a job

These would ideally all be exposed via the TriggerClient class and would require the Server API Key to access.

_TRI-1135

[ericallam]

/bounty $200

[algora-pbc]

## 💎 $200 bounty • Trigger.dev (YC W23)

### Steps to solve:
1. Start working: Comment /attempt #388 with your implementation plan
2. Submit work: Create a pull request including /claim #388 in the PR body to claim the bounty
3. Receive payment: 100% of the bounty is received 2-5 days post-reward. Make sure you are eligible for payouts

Thank you for contributing to triggerdotdev/trigger.dev!

Add a bounty • Share on socials

[xDesa]

/attempt #388

Options

• Cancel my attempt

[neo773]

/attempt #388

Options

• Cancel my attempt

[algora-pbc]

@fvckDesa is already attempting to complete #388 and claim the bounty. If you attempt to complete the same issue, there is a chance that @fvckDesa will complete the issue first, and be awarded the bounty. Try discussing with @fvckDesa and potentially collaborating on the same solution versus creating an alternate solution.

[matt-aitken]

@ericallam you can already get runs for a job, and get info about a run using the SDK

[ericallam]

@matt-aitken private data or just public?

[ericallam]

BTW the reason I created this issue is because of this scenario:

#386 (comment)

[ericallam]

Hold off on working on this for now, I think there's a discussion that needs to be had first about if it makes sense to use the Project API Key's for these management API endpoints or if we should have another type of API key that works across projects & environments. A sort of "Personal Access Token" type API Key, similar to the Supabase Management API works