fc.agent maintenance reboots: warm -> cold is not significant

[osnyx]

@ctheune and I have decided that there is no good reason for making the change of a warm to a cold reboot trigger a reschedule and customer notification.

PL-133301

@flyingcircusio/release-managers

Release process

• Created changelog entry using ./changelog.sh

PR release workflow (internal)

• PR has internal ticket
• internal issue ID (PL-…) part of branch name
• internal issue ID mentioned in PR description text
• ticket is on Platform agile board
• ticket state set to Pull request ready
• if ticket is more urgent than within the next few days, directly contact a member of the Platform team

Design notes

• Provide a feature toggle if the change might need to be adjusted/reverted quickly depending on context. Consider whether the default should be on or off. Example: rate limiting.
• All customer-facing features and (NixOS) options need to be discoverable from documentation. Add or update relevant documentation such that hosted and guided customers can understand it as well.

Security implications

• Security requirements defined? (WHERE)
  • reduce postponing of scheduled maintenances when not necessary
  • no need to notify customers due to implementation specifics (warm and cold reboot have the same apparent consequences for customers)
• Security requirements tested? (EVIDENCE)
  • adjusted unit test
  • automated tests still pass