Added Scheduling DB module

[GoodforGod]

Added Scheduling DB module

Merge after #667

[github-actions]

Test Results

727 tests   718 ✅  27m 56s ⏱️
 99 suites    9 💤
 99 files      0 ❌

Results for commit f4ba9e7.

♻️ This comment has been updated with latest results.

[GoodforGod]

Привет @strelchm спасибо за обзор, можешь еще повторно взглядом пройтись

[github-actions]

Dependency Update Report

Update level: patch

Found 3 dependency updates.

gradle/libs.versions.toml

• s3client-aws (software.amazon.awssdk:s3, inline:249): 2.47.5 -> 2.47.6
• zeebe: 8.9.12 -> 8.9.13
• kotlin-stdlib: 2.4.0 -> 2.4.10

[GoodforGod]

EN

Added explicit JSON payload codec registration for dynamic db-scheduler jobs. Payload types annotated with @Json and @SchedulingDbJsonCodec now get generated SchedulingDbCodec<T> components, while unknown payloads keep using the default Java serializer and built-in Void/null jobs avoid fallback serialization.

---

RU

Добавлена явная регистрация JSON-кодеков для payload-типов динамических задач db-scheduler. Типы с @Json и @SchedulingDbJsonCodec получают сгенерированный компонент SchedulingDbCodec<T>, неизвестные payload-типы продолжают использовать стандартный Java-сериализатор, а встроенные задачи с Void/null не дергают fallback-сериализацию.

---

• Added neutral SchedulingDbCodec<T> payload serialization abstraction discovered by SchedulingDbSerializer.
• Added @SchedulingDbJsonCodec for JSON-backed dynamic job payloads with generated SchedulingDbCodec<T> components.
• Added serializer fallback behavior for unknown payload types via db-scheduler's default Java serializer.
• Added hardcoded Void/null payload handling so built-in Kora scheduling jobs avoid fallback serialization.
• Added dedicated Java AP and KSP processors for @SchedulingDbJsonCodec.

---

SchedulingDbJsonCodec

A dynamic job payload can opt into JSON serialization:

@Json
@SchedulingDbJsonCodec
public record EmailJobData(String email, String subject) {}

The scheduling processors generate a Kora module that provides SchedulingDbCodec<EmailJobData> using TypeRef<EmailJobData>, JsonReader<EmailJobData>, and JsonWriter<EmailJobData>.

A user job can then use this payload type in a db-scheduler task descriptor:

@Module
public interface EmailSchedulingModule {

    TaskDescriptor<EmailJobData> EMAIL_TASK =
        TaskDescriptor.of("email", EmailJobData.class);

    @DefaultComponent
    default SchedulingDbJob emailSchedulingJob(EmailSender sender) {
        var task = Tasks.custom(EMAIL_TASK)
            .execute((instance, context) -> {
                var data = instance.getData();
                sender.send(data.email(), data.subject());
                return new CompletionHandler.OnCompleteRemove<>();
            });

        return () -> task;
    }
}

Application code can inject the exposed Scheduler and schedule task instances with typed payload data:

@Component
public final class EmailJobScheduler {

    private final Scheduler scheduler;

    public EmailJobScheduler(Scheduler scheduler) {
        this.scheduler = scheduler;
    }

    public void scheduleEmail(String email, String subject, Instant runAt) {
        var data = new EmailJobData(email, subject);
        var instance = EmailSchedulingModule.EMAIL_TASK
            .instance("email-" + email)
            .data(data);

        this.scheduler.schedule(instance, runAt);
    }
}

The payload is serialized through the generated SchedulingDbCodec<EmailJobData>. If no codec is registered for a payload type, SchedulingDbSerializer falls back to db-scheduler's default Java serializer. Built-in Kora jobs use Void/null payloads and are handled by a small sentinel path without invoking fallback serialization.