bug: inconsistent spaces in character married_to #788

Description

A character's married_to value can look identical in v4 and v5 but fail a direct string equality comparison because the space has a different Unicode code point.

Steps to reproduce

1. Fetch https://api.tibiadata.com/v4/character/Maltusia.
2. Fetch https://api.tibiadata.com/v5/character/Maltusia.
3. Compare character.character.married_to from the two responses.

Actual behavior

Observed on 2026-10-19:

The names render alike, but direct equality returns false.

Expected behavior

Return regular spaces (U+0020) consistently in married_to, regardless of API version or upstream source.

Investigation

• Maltusia's fansite API JSON response supplies "spouse":"Lando Atryda" with a regular space.
• The HTML source supplies Lando Atryda, which decodes to a non-breaking space.
• The existing Trollefar fixtures show the same upstream difference: HTML contains Mighty\u00A0troll, while fansite JSON contains Mighty troll.
• The current HTML parser already calls TibiaDataSanitizeStrings for married_to, converting non-breaking spaces to regular spaces. The fansite JSON parser copies spouse directly without this normalization.
• The live v4 discrepancy has not been explained by the current HTML parser; deployment differences have not been verified.

Scope

Keep the fix limited to spouse names: normalize U+00A0 to U+0020 in the fansite API spouse mapping and retain HTML/JSON parity coverage in TestCharacterTrollefar. No broader normalization of other character fields is requested.