[pattersonlois]

Fixes normalization and comment/string issues in examples/remarketing/upload_enhanced_conversions_for_leads.py and examples/remarketing/upload_enhanced_conversions_for_web.py:

1. Email normalization (normalize_and_hash_email_address):

   • Restores the gmail.com / googlemail.com domain check removed in Fix example to also normalize plus character in emails #1050 so periods and + suffixes are only stripped for gmail.com and googlemail.com addresses, matching the Google Ads API email normalization guidelines.
   • Replaces str.maketrans("", "", ".+") (which only stripped the literal + character) with .replace(".", "") and re.sub(r"\+.*$", "", email_parts[0]) to remove + and all subsequent characters up to @.

2. Whitespace normalization (normalize_and_hash):

   • Uses re.sub(r"\s+", "", s).lower() instead of s.strip().lower() so intermediate spaces in phone numbers (such as "+1 800 5550102") are stripped to produce valid E.164 format ("+18005550102").

3. Typos, comments, and CLI descriptions:

   • Fixes f"order ID {result,order_id}." -> f"order ID {result.order_id}." and missing space in upload_enhanced_conversions_for_web.py.
   • Fixes SHA-265 -> SHA-256 docstring typo, ArgumentParser descriptions, comment inaccuracies, and doubled quote typos ("..."" and '{ex.request_id}'') in both files.

[aleksUIX]

normalize_and_hash() also builds hashed_first_name and hashed_last_name in the web example, so this change hashes Mary Jane as maryjane. The enhanced-conversions guide and its Java/PHP address examples preserve internal spaces. These are different identifiers for matching. Can we keep trim-and-lowercase for names, remove internal whitespace only for phone numbers, and add a regression test with a multiword first or last name?