fix: lock attach table's snapshot location

[dantengsky]

I hereby agree to the terms of the CLA available at: https://docs.databend.com/dev/policies/cla/

Summary

During instantiating attach table instance, "lock" table's snapshot location( which is extracted from the last_snapshot_hint file), by

• putting the snapshot location extracted from hint file into table_info's options as the value of opt key OPT_KEY_SNAPSHOT_LOCATION
• for those table instances that created "from" the above table_info, they will use the same snapshot location

NOTE:

[databend_common_base::runtime::Runtime::block_on] (not tokio's) is used to execute async code within a sync context. It seems to be safe (not blocking other async tasks), but I am not quite sure.

@zhang2014 Please help review this usage.

Tests

• Unit Test
• Logic Test
• Benchmark Test
• No Test - use existing tests

Type of change

• Bug Fix (non-breaking change which fixes an issue)
• New Feature (non-breaking change which adds functionality)
• Breaking Change (fix or feature that could cause existing functionality not to work as expected)
• Documentation Update
• Refactoring
• Performance Improvement
• Other (please describe):

---

This change is