v0.6.0 – Replace Test Landing Table with v2_landing_test

Highlights

• Switched the test-profile landing table from landing_test to v2_landing_test.
• Updated active SDK scripts, ETL tools, integration tests, unit tests, and documentation to use the new test table.
• Added and verified the new v2_landing_test with the current schema and HASH(job_id) partitioning.
• Preserved the original landing_test table for legacy diagnostics and dldb investigation.
• Removed obsolete one-time landing migration and production smoke-test scripts.
• Production table defaults and behavior remain unchanged.

Breaking Changes

• WT_SDK_PROFILE=test now reads from and writes to v2_landing_test.
• The v2_landing_test table must exist before running test-profile integrations or operational commands.
• The old landing_test table is no longer the default test table, but can still be selected explicitly when needed.