Error in database query in every page

I am using version 4.91 and, in every page in my site, I get this error:

Query: CREATE TABLE wp_bill_site_integrity_issues ( id BIGINT UNSIGNED NOT NULL AUTO_INCREMENT, -- File identification and location file_path VARCHAR(500) NOT NULL COMMENT 'Relative file path from WordPress root', file_hash VARCHAR(64) COMMENT 'Current SHA-256 hash of the file', plugin_slug VARCHAR(100) COMMENT 'Plugin slug for plugin-related issues', -- Issue classification and details issue_type VARCHAR(30) NOT NULL, severity VARCHAR(10) DEFAULT 'medium' COMMENT 'Issue severity: low|medium|high|critical', description TEXT COMMENT 'Detailed description of the issue', -- User workflow and review status status VARCHAR(20) DEFAULT 'detected' COMMENT 'Current status: detected|reviewed|ignored|fixed|quarantined|deleted', reviewed BOOLEAN DEFAULT FALSE COMMENT 'Whether user has reviewed the issue', reviewed_at DATETIME COMMENT 'Timestamp when user reviewed the issue', user_action VARCHAR(20) COMMENT 'Action taken: ignore|repair|delete|quarantine', user_notes TEXT COMMENT 'User comments or notes about the issue', -- Temporal tracking metadata first_detected DATETIME DEFAULT CURRENT_TIMESTAMP COMMENT 'First detection timestamp', last_detected DATETIME DEFAULT CURRENT_TIMESTAMP COMMENT 'Most recent detection timestamp', resolved_at DATETIME COMMENT 'When the issue was resolved', -- Technical data for analysis and repair expected_hash VARCHAR(64) COMMENT 'Expected SHA-256 hash for core files', file_size INT UNSIGNED COMMENT 'File size in bytes', permissions VARCHAR(4) COMMENT 'File permissions (e.g., 0644, 0755)', file_owner VARCHAR(50) COMMENT 'File owner user/group', last_modified DATETIME COMMENT 'Actual file modification timestamp', -- Scanner and detection metadata scanner_version VARCHAR(20) COMMENT 'Version of scanner that detected issue', scan_id VARCHAR(50) COMMENT 'Unique identifier for the scan session', detection_method VARCHAR(30) COMMENT 'Method used: hash_check|signature|heuristics', -- Duplicate prevention and occurrence tracking occurrence_count INT UNSIGNED DEFAULT 1 COMMENT 'Number of times this issue was detected', is_active BOOLEAN DEFAULT TRUE COMMENT 'Whether issue is still present/active', -- Audit and maintenance fields created_at DATETIME DEFAULT CURRENT_TIMESTAMP, updated_at DATETIME DEFAULT CURRENT_TIMESTAMP ON UPDATE CURRENT_TIMESTAMP, PRIMARY KEY (id), -- Performance indexes INDEX idx_file_path (file_path(100)), INDEX idx_plugin_slug (plugin_slug), INDEX idx_issue_type (issue_type), INDEX idx_severity (severity), INDEX idx_status (status), INDEX idx_reviewed (reviewed), INDEX idx_is_active (is_active), INDEX idx_first_detected (first_detected), INDEX idx_last_detected (last_detected), INDEX idx_scan_id (scan_id(20)), -- Composite indexes for common queries INDEX idx_active_unreviewed (is_active, reviewed, severity), INDEX idx_type_severity (issue_type, severity, is_active), INDEX idx_detection_timeline (first_detected, last_detected, is_active), -- Unique constraint to prevent exact duplicate active issues UNIQUE KEY uniq_active_file_issue (file_path(200), issue_type, is_active), -- Fulltext search for descriptions and user notes FULLTEXT KEY ftx_search (description, user_notes) ) DEFAULT CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_520_ci

Requestor:

1. BillSecurity\IntegrityScanner\Bill_Catch_Malware->restore_classic_widgets_create_integrity_table()
   wp-content/plugins/restore-classic-widgets/includes/catch-malware/class_bill_catch_malware.php:1677
2. BillSecurity\IntegrityScanner\Bill_Catch_Malware->__construct()
   wp-content/plugins/restore-classic-widgets/includes/catch-malware/class_bill_catch_malware.php:404
3. restore_classic_widgets_bill_hooking_catch_malware()
   wp-content/plugins/restore-classic-widgets/restore_classic_widgets.php:285
4. do_action('init')
   wp-includes/plugin.php:522

Error message: Specified key was too long; max key length is 767 bytes

Error code: 1071