Standardize job_id usage in tracing

[heemankv]

Standardize job_id usage in tracing

Description

We currently have inconsistent usage of job identifiers in our tracing implementation. In some places, we use job.id while in others we use job.internal_id (often paired with block_no). This inconsistency makes tracing analysis and debugging more difficult.

For example, in the following code snippet:

log_type = "starting",
category = "snos",
function_type = "process_job",
job_id = ?job.id,

Problem

This inconsistency creates several issues:

1. Makes it harder to correlate logs across different parts of the system
2. Requires mental context switching when analyzing logs
3. Can lead to confusion when debugging production issues

Proposal

Standardize on using job.id throughout our tracing implementation because:

• It provides a direct reference to the exact job that was running
• Makes debugging and monitoring more straightforward
• When using job.internal_id with block_no, the identifier can be ambiguous if jobs are retried

[heemankv]

Same for block number : #204 (comment)