Fix job timeout

[HeDo88TH]

As title says

[Copilot]

Pull request overview

This PR addresses long-running Hangfire jobs being re-dequeued (and effectively “timing out”) by making the MySQL storage invisibility timeout configurable, and adjusts DroneDB build wrappers to treat “build already in progress” as a benign condition.

Changes:

• Add HangfireInvisibilityTimeoutHours to AppSettings + default configuration, and surface it in the configuration UI.
• Apply the configured invisibility timeout to Hangfire MySQL storage options.
• Change HangfireUtils behavior on DdbBuildInProgressException to log and skip instead of sleeping/retrying inline.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
Registry.Web/Utilities/StartupExtenders.cs	Configures Hangfire MySQL storage InvisibilityTimeout from settings.
Registry.Web/Utilities/HangfireUtils.cs	Updates build wrappers’ handling of DdbBuildInProgressException.
Registry.Web/Services/Adapters/ConfigurationDataBuilder.cs	Exposes the new invisibility-timeout setting in the Cron Jobs configuration section.
Registry.Web/Models/Configuration/AppSettings.cs	Adds the new HangfireInvisibilityTimeoutHours setting with XML documentation and default.
Registry.Web/appsettings-default.json	Adds the default HangfireInvisibilityTimeoutHours value under AppSettings.

Suppressed comments (1)

Registry.Web/Utilities/HangfireUtils.cs:92

• Similar to BuildWrapper: when BuildPendingWrapper hits DdbBuildInProgressException it currently logs "skipping" but still continues to log "Done build pending", which can make the job look like it successfully processed pending builds even though it did no work.

        catch (DdbBuildInProgressException ex)
        {
            // Benign: the lock holder will process the pending builds. See BuildWrapper.
            writeLine($"Build lock currently held by another process ({ex.Message}); skipping");
        }