[Task]: Refactor ModularityKit.Mutator.Governance.Redis.Tests into focused fixtures

[rian-be]

Summary

Refactor ModularityKit.Mutator.Governance.Redis.Tests into smaller, provider focused fixtures so Redis storage, serialization, keyspace, and query behavior remain easy to extend and review.

Goal

Improve maintainability of governance Redis tests by decomposing mixed provider fixtures, extracting stable specific test support where repetition is real, and aligning file boundaries with provider concerns.

Problem

ModularityKit.Mutator.Governance.Redis.Tests covers several provider concerns that will continue to grow as persistence and query behavior expand. Without more focused fixtures and clearer package local support, tests become harder to scan, harder to change safely, and harder to diagnose when provider behavior fails.

Scope

• Split oversized or mixed Redis governance test fixtures into focused files by provider concern
• Isolate serialization, keyspace, query, and persistence scenarios where they are currently coupled too closely
• Extract stable specific test support when setup or fixtures repeat inside the package
• Normalize naming so Redis governance test files and fixtures match the provider scenario they cover
• Keep refactoring scoped to ModularityKit.Mutator.Governance.Redis.Tests

Design Expectations

• Test decomposition should preserve provider behavior while making scenario boundaries clearer.
• Redis specific helpers should be extracted only where they remove real duplication.
• Fixture structure should keep storage and query behavior easy to trace during failures.
• File names and fixture names should reflect Redis provider concerns rather than mixed utility buckets.

Acceptance Criteria

• ModularityKit.Mutator.Governance.Redis.Tests no longer relies on oversized mixed concern fixtures for its core provider scenarios
• Serialization, keyspace, query, and persistence scenarios live in focused test files or fixtures
• Repeated Redis-specific setup is extracted only where it improves readability and reuse
• Naming across the package is more consistent and provider oriented

Non Goals

• This issue does not change Redis provider behavior or public APIs
• This issue does not refactor governance package tests outside the Redis test project
• This issue does not pull all provider test support into one cross package helper layer