Enum values that ignore naming conventions in Payment Handler API

[dontcallmedom-bot]

While crawling Payment Handler API, the following enum values were found to ignore naming conventions (lower case, hyphen separated words):

• The value "shippingAddress" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
• The value "payerName" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
• The value "payerPhone" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)
• The value "payerEmail" of the enum PaymentDelegation does not match the expected conventions (lower case, hyphen separated words)

See Use casing rules consistent with existing APIs in Web Platform Design Principles document for guidance.

_{This issue was detected and reported semi-automatically by Strudy based on data collected in webref.}

[ianbjacobs]

/cc @marcoscaceres

[rsolomakhin]

I'm inclined to ignore this warning. It's a bit late in API lifecycle to nitpick over enum value formatting. WDYT?