Improve name of orderNotes flag for checkout-state provider.

[nerrad]

While reviewing #2851, I left some feedback on choice of variable names for the account creation flag and noticed there's a similar problem with the naming around the orderNotes flag (added in #2877).

This issue is to address the orderNotes flag naming. It should better reflect that the property is a boolean. Maybe something like canLeaveOrderNotes. I realize it's more verbose, but it's immediately clear when parsing code it's purpose as opposed to orderNotes which on first glance I would assume is a list/collection of orderNotes.

[haszari]

This issue is to address the orderNotes flag naming. It should better reflect that the property is a boolean. Maybe something like canLeaveOrderNotes. I realize it's more verbose, but it's immediately clear when parsing code it's purpose as opposed to orderNotes which on first glance I would assume is a list/collection of orderNotes.

FYI @nerrad - I think this orderNotes state is text; either empty (no order note) or containing user-supplied note text. In the API response it's serialised as customer_note. I agree though it maybe could be clearer and more consistent throughout.

There is a boolean showOrderNotes block attribute, controlling whether the note UI is available to shopper. This might be clearer as allowOrderNotes.

[nerrad]

OHHH, I totally misunderstood then, I should have clued in from the type on the default that it was not a boolean flag 🤦 . Some good suggestions in your comment about renaming but it's not as critical as what I originally thought with flags. So I'll close the issue.