Create innodb_fts_threads variable to process the background fts message and optimization
of the table during idle time. By doing this, InnoDB can do sync/optimize
the multiple table at the same time. This could lead to reduce time for removing
the table from fts_optimize queue.

Points to consider:

1) DELETE_MESSAGE should be processed after inserting the table into the slot
and wait for concurrent sync or optimization to complete
2) Try to use existing thread pool mechanism for it
3) Try to reduce the usage of THD* object for sync message (in case more fts threads)
4) While reducing the number of threads(1), InnoDB shouldn't hang while drop
the table.

Here by attaching prototype patch using thread pool and normal THD approach.
I did use normal THD approach and later @marko suggested me to use existing
thread pool. So attaching both patches for future reference.