Rename fetch flags

[jonsnyder]

Description

As recommended by Erik Wiener:

I see the use of "notification" to refer to proposition interactions or events in the docs and in the code, e.g. sendDisplayNotifications and includePendingDisplayNotifications. I personally think it would be better to avoid the term "notification", which is a Target concept, and instead try to align around "proposition", "proposition interaction", and "event", which are solution-agnostic terms. Those two new parameters above stick out to me because I don't think we've tended to use the term "notification" in public docs related to personalization (though I could be wrong). I feel it would be more consistent to use names like sendDisplayEvent and includeRenderedPropositions.

I think of the whole event as the notification, and the proposition interactions inside _experience.decisioning.propositions as the experiences that are the subject of the event (i.e. what personalization experiences were interacted with as part of that event).

Related Issue

Motivation and Context

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Improvement (non-breaking change which does not add functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• I have signed the Adobe Open Source CLA or I'm an Adobe employee.
• I have made any necessary test changes and all tests pass.
• I have run the Sandbox successfully.

[jfkhoury]

I love this change! Do we need to update anything in the docs?