What this PR does / why we need it:

RemoteRegistry.apply_saved_dataset() (sdk/python/feast/infra/registry/remote.py) builds an ApplySavedDatasetRequest, but sends it through the ApplyFeatureService RPC instead of the dedicated ApplySavedDataset RPC:

def apply_saved_dataset(
    self,
    saved_dataset: SavedDataset,
    project: str,
    commit: bool = True,
):
    request = RegistryServer_pb2.ApplySavedDatasetRequest(
        saved_dataset=saved_dataset.to_proto(), project=project, commit=commit
    )
    self.stub.ApplyFeatureService(request)  # <-- wrong RPC

The server (sdk/python/feast/registry_server.py) already implements a correct ApplySavedDataset handler that expects exactly this request shape and forwards it to proxied_registry.apply_saved_dataset(...). Because the client calls ApplyFeatureService instead, the server tries to handle an ApplySavedDatasetRequest payload through the ApplyFeatureService RPC/ApplyFeatureServiceRequest shape, so registering a SavedDataset against a remote registry (registry_type: remote) never reaches the intended handler and the saved dataset is not correctly persisted.

This was found while working with a Feast deployment using a remote registry (Feast Operator / OpenShift), trying to register a SavedDataset via store.registry.apply_saved_dataset(...) after using store.create_saved_dataset()'s .persist() step wasn't an option for the offline store in use.

The fix is a one-line change: call self.stub.ApplySavedDataset(request) instead of self.stub.ApplyFeatureService(request).

Which issue(s) this PR fixes:

None filed yet — I searched open/closed issues and PRs for ApplySavedDataset / apply_saved_dataset and didn't find an existing report.

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

Added test_apply_saved_dataset_calls_apply_saved_dataset_rpc to sdk/python/tests/unit/infra/registry/test_remote_registry.py, following the existing remote_registry fixture pattern in that file. Verified locally:

• Test fails against the pre-fix code (ApplyFeatureService.assert_not_called() fails because it was called).
• Test passes with the fix applied, and confirms the request payload (ApplySavedDatasetRequest) is unchanged, only the RPC method changes.
• Full test_remote_registry.py suite (5 tests) passes.

Misc

Small, isolated fix — one production line changed, plus a regression test. No API changes.