update standard ecommerce params

[dgitis]

Description & motivation

I realize now that when I set up the first recommended events, I only included required fields as documented here. In other cases, I or others included fields that aren't required in the recommended events, like item_list_name and item_list_id in the view_item_list event.

This PR adds those non-required parameters to ecommerce events.

I realize now that we should have a discussion on how to handle it. We either only add the required fields and then make our documentation clear that fields that aren't marked as required need to be added as custom parameters, or we default to adding all of the parameters listed in the recommended events docs.

Checklist

• I have verified that these changes work locally
• [] I have updated the README.md (if applicable)
• [ n/a] I have added tests & descriptions to my models (and macros if applicable)
• I have run dbt test and python -m pytest . to validate existing tests

[dgitis]

I should have opened an Issue to discuss this first, but only realized what the issue was when I was preparing a PR. @adamribaudo and @willbryant, please comment on whether to include event parameters from recommended events that are documented but not required in our staging models.

[adamribaudo-velir]

I don't have a strong opinion here. This is clearly an improvement from the current state so I'm happy to merge.