Changing job_id type from Int to BigInt

[gyli]

Description

Changing job_id type from Int to BigInt to support more task executions.

Use case/motivation

Current type of job_id in taskinstance is int, which has a reachable limit 2147483647 for users who have many DAG runs or many tenants. Once it's reached, task won't start new execution due to error from db.
For better potential multi-tenancy support, I believe it would be much safer if the job_id type can be changed to BigInt.

Related issues

No response

Are you willing to submit a PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.

[uranusjr]

Since this is ultimately a pk in Job, even BigInt sounds reachable considering it’s ever incremental. A UUID or another solution may be more desirable.

[uranusjr]

Adding this as a possible candidate since it’s arguably a breaking change. Although we could justify this later on, it’d be easiest to bundle it into 3.0.