Fix: Managing the availability of the clear logs button on Log page

[IgorA100]

The delete logs button now remains active even after deleting logs (both successful and unsuccessful).
This PR allows for more accurate management of the button's availability.

• After clicking the delete logs button, the button becomes unavailable to avoid repeated clicks, as the bootstrap table can take a long time to update, allowing time for another click of the delete logs button.
• After each table update is complete, a check is made to determine whether rows are selected, and the availability of the clear logs button is determined based on this.
• After clicking the "Cancel" button in the modal confirmation window, the selected rows in the table are checked, and the availability of the clear logs button is determined based on this.
• If an error occurs executing the AJAX request to delete logs, the selected table rows are also analyzed, and the availability of the clear logs button is determined based on this.

[Copilot]

Pull request overview

This PR refines the Log page clear-logs button state so users cannot repeatedly trigger log deletion while the modal or table refresh is in progress.

Changes:

• Disables the clear-logs button immediately after it is clicked.
• Re-checks selected rows after table load success and AJAX modal-loading failures.
• Extracts clear button enable/disable logic into manageClearButtonAvailability().

---

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

[IgorA100]

@connortechnology
I consider this PR complete.