Temporal Tables: Invalid migrations generated for some complex migrations, e.g. involving schema manipulation

Some complex migrations involving temporal tables don't work properly. Those usually involve some schema manipulation and/or cases that can happen when multiple migrations are combined into one (e.g. convert table to temporal + table rename).

Example scenarios:

Temporal_multiop_add_column_to_temporal_table_with_default_schemas_change_default_schema_add_another_column (key not found)

Temporal_multiop_convert_regular_table_to_temporal_change_default_schema_convert_back_to_regular (key not found)

Temporal_multiop_create_regular_convert_to_temporal_rename_table_drop_column (trying to access invalid object)

Temporal_multiop_drop_temporal_create_normal_add_column_rename_convert_to_temporal_drop_create_again_as_temporal_convert_to_normal_edit_drop (versioning not turned on for renamed table when necessary)