Add offending view name to error logs in view_migrate

[rohany395]

Resolves #4438

Problem

When migrate-tables fails to analyze a view's SQL in view_migrate.py,
the error and log messages include the view's DDL but not the view's name.
With many views processed in parallel, this makes it hard to identify which
view caused the failure.

Change

Adds the offending view's key (self.src.key) to the three failure sites in
ViewToMigrate._view_dependencies:

• The ValueError raised on a sqlglot ParseError
• The ValueError raised when parsing yields no usable statement
• The logger.error emitted when a referenced table's schema can't be determined

Tests

Extended test_sequence_view_with_invalid_query_raises_value_error to assert
the offending view's key appears in the raised error message.

Note on scope

This PR is scoped to the logging improvement requested
("at a minimum add logging"), which also provides the diagnostics needed
to confirm the offending view and DDL when investigating that underlying
parsing behavior.

[CLAassistant]

All committers have signed the CLA.