feat(Reboot): increase reboot count down time

[ArgoZhang]

Link issues

fixes #7334

Summary By Copilot

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Enhancements:

• Adjust the FlipClock countdown start value from 140 to 240 seconds in the reboot UI component to extend the allowed reboot preparation time.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Increases the reboot countdown duration displayed by the FlipClock component from 140 to 240 seconds in the RebootCountDown UI component.

File-Level Changes

Change	Details	Files
Extend reboot countdown duration in the RebootCountDown UI.	Update FlipClock StartValue to use a 240-second TimeSpan instead of 140 seconds	src/BootstrapBlazor.Server/Components/Components/RebootCountDown.razor

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#7334	Increase the reboot countdown duration in the RebootCountDown component.	✅

Possibly linked issues

• feat(Reboot): increase reboot count down time #7334: PR directly implements the issue by changing the reboot countdown StartValue from 140 to 240 seconds.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey there - I've reviewed your changes - here's some feedback:

• Consider extracting the countdown duration from a hard-coded TimeSpan.FromSeconds(240) into a named constant or configuration setting so it’s easier to adjust and keep consistent across any other reboot-related components.
• If there is any user-facing text or labels describing the reboot countdown duration elsewhere in the UI, make sure those are updated to match the new 240-second value to avoid confusing users.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- Consider extracting the countdown duration from a hard-coded `TimeSpan.FromSeconds(240)` into a named constant or configuration setting so it’s easier to adjust and keep consistent across any other reboot-related components.
- If there is any user-facing text or labels describing the reboot countdown duration elsewhere in the UI, make sure those are updated to match the new 240-second value to avoid confusing users.

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[Copilot]

Pull request overview

This PR increases the reboot countdown timer duration from 140 seconds (2 minutes 20 seconds) to 240 seconds (4 minutes) to provide more time for users during website reboot/update operations.

Key Changes:

• Extended the countdown duration in the RebootCountDown component to allow more time for server restarts

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b1f9ed5) to head (bc7ce3c).
⚠️ Report is 2 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main     #7335   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files          747       747           
  Lines        32760     32760           
  Branches      4540      4540           
=========================================
  Hits         32760     32760           

Flag	Coverage Δ
BB	100.00% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.