Avoid chaining duplicated semian identifiers in error messages

[casperisfine]

When errors are created from other errors messages they might already have a semian identifier in their message

[adrianna-chang-shopify]

Makes sense to me! Is there anywhere in the repo where we're currently constructing an error from another error's message where this was a problem? Or is this just a future-proofing fix?

[adrianna-chang-shopify]

Suggested change

	# When errors are created from other errors messages they might
	# When errors are created from other errors' messages they might

Or maybe singularize it?

Suggested change

	# When errors are created from other errors messages they might
	# When an error is created from another error's message it might
	# already have a semian identifier in the message

[casperisfine]

Is there anywhere in the repo where we're currently constructing an error from another error's message where this was a problem?

Not in the repo, but redis-rb 5.0 does this a lot with redis-client errors: https://github.com/redis/redis-rb/blob/d4b24e1e4fac7b9e3fee01947bf400f52ea500cf/lib/redis/client.rb#L118-L126

[miry]

I think it should be mentioned in Changelog as well.

[casperisfine]

Done.