fix(physical-restore): InnoDB FTS Index Repair

[tanmoysrt]

In physical restore, FTS index can't be restored anyway. So, we need to re-create it.

Ref - https://dev.mysql.com/doc/refman/8.4/en/innodb-table-import.html

---

Already attempted the re-creation of InnoDB indexes here (ref) -
Whatever MariaDB docs tell, doesn't work as it is for physical restore (mysql at-least has some good docs)

InnoDB FullText Index Repair -

• Drop the FTS indexes from table first

• OPTIMIZE TABLE for that specific table to fix corruptions.
  If we don't do it, there will be almost no noticable issues. But, on fulltext index creation database will crash.

   2025-03-10 09:37:32 0x7ff50c221700  InnoDB: Assertion failure in file /home/buildbot/buildbot/build/mariadb-10.6.21/storage/innobase/pars/pars0pars.cc line 771
   InnoDB: Failing assertion: sym_node->table != NULL
   250310  9:37:32 [ERROR] /usr/sbin/mariadbd got signal 6 ;
   Query (0x7ff3c4010c30): ALTER TABLE `tabHD Ticket` ADD FULLTEXT INDEX `hd_ticket_content`
  

• Create the FTS indexes again.

---

edit: Actually dropping index might be just modify metadata and in FULLTEXT they have it's own data structure + ibd files. That might be creating this issue (?).