feat(connectors): BI-6586 Support YDB VIEW

[catsona]

No description provided.

[Copilot]

Pull request overview

This PR adds support for YDB VIEW objects by enabling views to be treated similarly to tables in queries and dataset operations. The changes enable YDB views functionality through feature flags and update the connector to properly handle view objects alongside tables.

• Enables YDB view support via feature flag configuration
• Updates table listing logic to include view objects
• Implements custom column info retrieval for views using subselect queries

Reviewed changes

Copilot reviewed 7 out of 8 changed files in this pull request and generated 1 comment.

Show a summary per file

File	Description
lib/dl_sqlalchemy_ydb/dl_sqlalchemy_ydb/dialect.py	Updates type hint to accept integer values in interval processing
lib/dl_connector_ydb/pyproject.toml	Fixes relative path reference for dl-sqlalchemy-ydb dependency
lib/dl_connector_ydb/docker-compose.yml	Adds feature flag to enable views in YDB test environment
lib/dl_connector_ydb/dl_connector_ydb_tests/db/api/test_dataset.py	Adds test class for view-based datasets
lib/dl_connector_ydb/dl_connector_ydb_tests/db/api/base.py	Implements test fixture base class for YDB view testing
lib/dl_connector_ydb/dl_connector_ydb/core/ydb/adapter.py	Updates table listing to include view objects
lib/dl_connector_ydb/dl_connector_ydb/core/base/adapter.py	Implements custom column info retrieval for views using subselects

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Copilot]

The error message should be more descriptive and include the actual paths to help debugging. Consider: f'Absolute table path {table_def.table_name} is not a subpath of database path {table_def.db_name}'

Suggested change

	raise ValueError("absolute table path is not subpath of database path")
	raise ValueError(
	f"Absolute table path '{table_def.table_name}' is not a subpath of database path '{table_def.db_name}'"
	)

[KonstantAnxiety]

1. Is this scenario actually possible? If it is, let's create a test for it
2. Is ValueError suitable here? Won't it fire as a 5xx from the API?