fix: handle non-string input in Replace validator gracefully

[gaoflow]

The Replace validator calls re.Pattern.sub() directly on the input value. When passed a non-string type (int, None, list, etc.), this raises an unhandled TypeError instead of the expected Invalid exception.

This matches the behavior of the Match validator, which already catches TypeError and raises a proper Invalid error with a descriptive message.

Before (crashes):

>>> from voluptuous.validators import Replace
>>> Replace('hello', 'goodbye')(42)
TypeError: expected string or bytes-like object, got 'int'

After:

>>> from voluptuous.validators import Replace
>>> Replace('hello', 'goodbye')(42)
voluptuous.error.MatchInvalid: expected string or buffer

Changes:

• Replace._call_ now catches TypeError and raises MatchInvalid
• Added test_replace_non_string_input covering int, None, list, and custom message cases

[gaoflow]

Rebased onto master and dropped the unrelated quote-style churn from the diff — it's now just the Replace fix and its test.