Improvement to scheduling widget: Options for scheduling content publication or archiving

Problem/Motivation

Challenges have been encountered with the current "Schedule a status change" button in the lightning_scheduler module. The existing user interface is not intuitive, especially when scheduling content state changes such as publishing or archiving. As a result, users struggle to understand when scheduled changes will take effect, and the interface requires extra steps for selecting scheduling options.

Steps to reproduce

1. Install and enable the lightning_scheduler module.
2. Attempt to schedule a state change for a content item using the "Schedule a status change" button.
3. Observe the lack of clear options for scheduling changes and the need for multiple steps to configure the scheduling.

Proposed resolution

The following improvements are suggested to enhance the user experience:

1. Remove the standard "Schedule a status change" button.
2. If the status field is set to "Published" or "Archived," display radio buttons labeled "When to publish:" or "When to archive:" with options "Now" (selected by default) and "Later".
3. If "Later" is selected, display date and time fields immediately below the selection.
4. Add this description under the radio buttons: "Scheduled state changes may take up to 10 minutes to take place, after the specified time."

Remaining tasks

• Get feedback from the maintainer on whether this approach aligns with the direction of the module.
• If approved, implement the proposed changes.
• Update the documentation to reflect the new functionality.
• Test the changes and ensure backward compatibility.

User interface changes

The proposed changes will introduce a new set of radio buttons to replace the "Schedule a status change" button, along with date and time fields for scheduling future state changes. These changes aim to make the scheduling process more intuitive and user-friendly.

API changes

No API changes are expected as part of this feature request.

Data model changes

No changes to the data model are anticipated for this feature request.