Avoid MongoDB write conflicts in MongoJobRepository by replacing sequence-based ID with TSID

[diydriller]

Summary

This PR addresses a concurrency issue in the MongoDBJobRepository.

The current implementation generates numeric identifiers for job/step executions through a sequence document.
Under concurrency, especially with transactional writes, this causes frequent WriteConflict errors from MongoDB.

This PR replaces the numeric sequence generation with application-generated, unique, time-ordered identifier.
This eliminates write conflicts caused by sequence updates.

Problem

MongoDB uses optimistic concurrency control, and concurrent writes to the same document cause conflicts.

collection.findOneAndUpdate(
    new Document("_id", sequenceName),
    new Document("$inc", new Document("count", 1)),
    options
).getLong("count");

This produces high contention on a single document under parallel workloads.

Solution

Replace sequence-based numeric ID generation with TSID.
Implements TSID algorithm(42-bit timestamp + 10-bit node ID + 12-bit sequence)

TSID characteristics

• time-ordered
• unique
• 64-bit long value

Fixes #4960

[quaff]

It's still possible same nodeId is used by multiple instances resulting in conflicts.