feat: Add SingleStore online store support for feature view versioning

[antznette1]

What this PR does / why we need it:

This PR adds online feature view versioning support for the SingleStore online store when registry.enable_online_feature_view_versioning is enabled.

It updates SingleStore’s table routing to read/write from versioned namespaces (e.g. {project}_{feature_view}_v{N}) so version-qualified refs like driver_stats@v1:avg_daily_trips can be served from the correct underlying online table. It also updates the global online-store guard to allow version-qualified reads for SingleStore (and still reject unsupported stores) when versioning is enabled.

Additionally, it adds an integration/universal test covering SingleStore version-qualified reads.

Which issue(s) this PR fixes:

Fixes #6181

Checks

• I've made sure the tests are passing.
• My commits are signed off (git commit -s)
• My PR title follows conventional commits format

Testing Strategy

• Unit tests
• Integration tests
• Manual tests
• Testing is not required for this change

Misc

Notes:

• Version-qualified reads are only allowed when registry.enable_online_feature_view_versioning is enabled; otherwise VersionedOnlineReadNotSupported is raised.
• The new SingleStore integration/universal test may be skipped locally if the universal SingleStore environment is not part of the parametrized test matrix (it should run in CI where SingleStore is enabled).

---

[antznette1]

Good day @franciscojavierarceo
I have created the PR, awaiting your review.

[ntkathole]

@antznette1 Can you please take a look at #6193, it has shared helper added now for table name and pattern for deleting all versions in teardown ?

[antznette1]

@ntkathole , Please can I get a review to this PR?

@antznette1 Sure, please fix the conflicts and the tests

Conflicts has been fixed, can we proceed?

[antznette1]

@ntkathole , Please can I get a review to my PR?

[ntkathole]

@antznette1 Can you please take a look at #6193, it has shared helper added now for table name and pattern for deleting all versions in teardown ?

@antznette1 I mentioned this to see if we really need registry object passing down the calls or can be resolved with the same approach that PR to handle version cleanup ?

def teardown(self, config, tables, entities, registry=None) -> None:
    project = config.project
    versioning = config.registry.enable_online_feature_view_versioning
    with self._get_cursor(config) as cur:
        for table in tables:
            if not versioning:
                _drop_table_and_index(cur, project, table, enable_versioning=False)
            else:
                # Discover all versioned tables from DB — same as MySQL
                base = f"{project}_{table.name}"
                cur.execute(
                    "SELECT table_name FROM information_schema.tables "
                    "WHERE table_schema = DATABASE() AND "
                    "(table_name = %s OR table_name REGEXP %s)",
                    (base, f"^{base}_v[0-9]+$"),
                )
                for (name,) in cur.fetchall():
                    cur.execute(f"DROP INDEX IF EXISTS {_quote_identifier(name + '_ek')} "
                                f"ON {_quote_identifier(name)}")
                    cur.execute(f"DROP TABLE IF EXISTS {_quote_identifier(name)}")

[antznette1]

@ntkathole
I have done the requested fixes

[franciscojavierarceo]

can you elaborate on why some of the changes are included in this PR? feels like maybe some other items snuck in. 😅

[antznette1]

can you elaborate on why some of the changes are included in this PR? feels like maybe some other items snuck in. 😅

My bad.
The few unrelated changes snuck into this PR while I was iterating locally (PGVector container wait tweaks, metrics import fallback, and a HybridOnlineStore teardown refactor). They’re not required for SingleStore versioned online store support, so I’ll reverted them locally to keep this PR focused strictly on SingleStore versioning + teardown behavior. I’ll push the revert commit now.

[devin-ai-integration]

Devin Review found 1 new potential issue.

View 19 additional findings in Devin Review.

[antznette1]

Good day,
please, I am still waiting for a review on this PR

[antznette1]

Hello