test: add test for updating repeat job's data

[manast]

Why

We got a report of an issue (#3095 (comment)) and this test should cover that scenario.

How

Written a test that upserts a job scheduler several times and we check that the data of the next job associated with the scheduler is indeed updated.

Additional Notes (Optional)

N/A

[Copilot]

Pull Request Overview

Adds a new test case to verify that repeatedly upserting a job scheduler updates the data of its next scheduled job as expected.

• Introduces an it block that upserts a scheduler four times, checking the enqueued job’s .data after each update.
• Utilizes a fake clock (this.clock) to advance scheduling intervals deterministically.
• Validates that the job waiting in the queue always reflects the most recent data payload.

[Copilot]

This check occurs without advancing the fake clock, so the scheduler may not have enqueued the next job yet. Consider adding await this.clock.tickAsync(1); before retrieving waitingJobs3 for consistency with the other iterations.

Suggested change

	await this.clock.tickAsync(1);

[roggervalf]

Lgtm