Add "dom-action" schema only if PAGE_WIDE_SCOPE decisions are requested

[ninaceban]

Description

Personalization component should be sending "dom-action" schema ONLY when sendEvent(...) renderDecisions is set to true.

Related Issue

None

Motivation and Context

We should not send "dom-action" schema if whoever implements Alloy doesn't want decisions to be auto-rendered. This should also help the backend be a little bit more selective about the data it processes and returns.

Screenshots (if appropriate):

None

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.

[Aaronius]

A filename like personalizationConstants.js suggests that the focus of this file might not be narrow enough, especially since it's located under Personalization/constants. Rather than a bucket of all potential personalization constants, would it make more sense to have schema.js and scope.js files instead? Another thing to note is that personalizationConstants.js is plural whereas our convention is that the file should be singular (https://github.com/adobe/alloy/wiki/Conventions#enumerations).

[ninaceban]

thank you, will extract those in separate files

[jonsnyder]

The title of this PR is a bit misleading. Its really doing: Add "Dom-action" schema only if page wide scope is requested explicitly
or implicitly by setting renderDecisions = true.