fix: retry experimental and MLV operations

[Raki (mdrakiburrahman)]

Note

Thank you for making change! Please fill this template for your pull request to improve quality of check-in message.

Tip

This repo uses Conventional Commit conventions - please try to rename your PR headline to match it.

Warning

Please ensure to read through this whole set of instructions, specially the Test section.

Why this change is needed

Experimental streaming_table SQL bypassed the adapter connection manager and therefore ignored configured per-statement job retries. Transient failures from CREATE STREAMING TABLE or SHOW STREAMING TABLES failed immediately instead of honoring retry patterns and backoff.

Fixes #301.

How

Routes experimental streaming SQL through FabricSparkConnectionManager.add_query(..., auto_begin=False), preserving the owning-connection guard before consuming results. The same configured message-pattern policy now retries matching MLV on-demand refresh failures, and CI configures a narrow MLV_RUNTIME_ERROR pattern.

Also bumps the adapter to 1.13.8 and adds the release changelog.

Test

Important: Non-Microsoft Employee contributors

If you are not a Microsoft employee with a foo@microsoft.com email, you will not be able to run CI as it runs in the @microsoft.com Fabric Tenant where you do not have access.

In order for your PR to be considered for review, you must attach a clear screenshot of the output of you running the following command successfully:

npx nx run dbt-fabricspark:test --output-style=stream

Targeted validation performed:

• uv run pytest tests/unit/test_experimental.py::test_execute_uses_connection_manager_query_path -vv — passed (1 test).
• uv run pytest tests/unit/test_mlv_api.py::TestRunOnDemandRefresh::test_retries_matching_configured_failure -vv — passed (1 test).
• npx nx run dbt-fabricspark:publish-blob --output-style=stream — passed; built and uploaded dbt_fabricspark-1.13.8-py3-none-any.whl.
• Full local regression suite was not run per the requested targeted-test scope; GitHub Actions will run it.

Microsoft Employee contributors

Your PR will be subjected to full regression suite via GitHub Action.
It's highly recommended to run the tests locally so your contributions are promptly merged rather than failing in CI.