[Backport 0.1] Fix recover index bug when Flint data index is deleted accidentally

[dai-chen]

Backport f4744ab from #241.

Note that the original PR depends on metadata log purge functionality introduced in #189. To avoid the possible impact and API changes, I only cherry-picked minimal code changes instead of the complete #189.

CREATE SKIPPING INDEX ON stream.lineitem_tiny
(l_shipdate VALUE_SET)
WITH ( auto_refresh = true );

# Delete Flint data index
DELETE flint_myglue_stream_lineitem_tiny_skipping_index

# Check index state metadata log
GET .query_execution_request_myglue/_search
      {
        "_index": ".query_execution_request_myglue",
        "_id": "ZmxpbnRfbXlnbHVlX3N0cmVhbV9saW5laXRlbV90aW55X3NraXBwaW5nX2luZGV4",
        "_score": 1,
        "_source": {
          "version": "1.0",
          "latestId": "ZmxpbnRfbXlnbHVlX3N0cmVhbV9saW5laXRlbV90aW55X3NraXBwaW5nX2luZGV4",
          "type": "flintindexstate",
          "state": "refreshing",
          "applicationId": "unknown",
          "jobId": "unknown",
          "dataSourceName": "myglue",
          "jobStartTime": 1706916312007,
          "lastUpdateTime": 1706916452474,
          "error": ""
        }
      }

spark-sql> RECOVER INDEX JOB flint_myglue_stream_lineitem_tiny_skipping_index;
24/02/02 23:48:31 WARN FlintSpark: Cleaning up metadata log as index data has been deleted

# The metadata log is gone
GET .query_execution_request_myglue/_search