Field naming: Adding a note for client side impact (#1355)

* Field naming - client side impact

* indentation

* Highlight the node and added changelog

---------

Co-authored-by: Noah Dietz <noahdietz@users.noreply.github.com>

Author: pinalbaldha

aip/general/0140.md

@@ -33,6 +33,9 @@ including adjectives that always apply and add little cognitive value. For
 example, a `proxy_settings` field might be as helpful as
 `shared_proxy_settings` if there is no unshared variant.
 
+**Important:** Field names often appear in generated client surfaces. Ensure they 
+are appropriately descriptive and of suitable length.
+
 ### Case
 
 Field definitions in protobuf files **must** use `lower_snake_case` names.
@@ -156,6 +159,7 @@ field **should not** have a uniqueness requirement.
 
 ## Changelog
 
+- **2024-05-18**: Documented the effect of field names on client surfaces.
 - **2023-04-25**: Field names **must not** be expressed as verbs.
 - **2021-07-12**: Normalized display name guidance to "should".
 - **2021-04-07**: Added base64 and bytes guidance.