ddl: Fix rename come after database has been dropped (#9274)

[ti-chi-bot]

This is an automated cherry-pick of #9274

What problem does this PR solve?

Issue Number: close #9266

Problem Summary:

In InterpreterRenameQuery, it use context.getDatabase which will throw an exception if the database instance is not exist in tiflash.

The database has been dropped in TiDB before TiFlash sync the schema diff of "create database". And the following rename table to that database (database_id=170) throw exception.

TiDB	TiFlash
create table db_2.t_166;
	sync create table db_2.t_166 and success
create database db_170;
rename table db_2.t_166 to db_170.t_166;
drop table db_170.t_166;
drop database db_170;
	raft-log comes after database has been dropped, tiflash begin its schema sync
	begin to sync create db_170 but failed sliently
	begin to sync rename db_2.t_166 to db_170.t_166 but exception thrown (crash here)

What is changed and how it works?

In SchemaBuilder::applyRenamePhysicalTable it should create a local IDatabase instance with a "fake" DBInfo if can not fetch from TiKV.

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Side effects

• Performance regression: Consumes more CPU
• Performance regression: Consumes more Memory
• Breaking backward compatibility

Documentation

• Affects user behaviors
• Contains syntax changes
• Contains variable changes
• Contains experimental features
• Changes MySQL compatibility

Release note

Fix a bug that TiFlash may panic when a database is created and then dropped quickly

[JaySon-Huang]

/run-all-tests

[JaySon-Huang]

/run-unit-test

[CalvinNeo]

lgtm

[ti-chi-bot]

[LGTM Timeline notifier]

Timeline:

• 2024-08-01 06:32:20.351411234 +0000 UTC m=+423856.631459303: ☑️ agreed by Lloyd-Pottiger.
• 2024-08-02 08:01:42.033662686 +0000 UTC m=+76499.252424295: ☑️ agreed by CalvinNeo.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: CalvinNeo, Lloyd-Pottiger

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [CalvinNeo,Lloyd-Pottiger]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment