Non-AEP customer updates

Issue in ./help/tutorial-web-sdk/configure-identities.md

Step 2 (picking a sandbox) doesn't apply to customers without an AEP license

It may also be important to call out that namespace identities can't be deleted. So for customers without an AEP license, this step will permanently create an identity namespace, even when they upgrade to AEM. Also, if a number of users at the same company do this tutorial, they will all see this this namespace and may not need to create it.

This section may also be a good place to start calling out that any AAM cross-device data sources will show up in the identity namespaces. And if they are using AAM with AEP, it may be better to simply use an existing AAM-created namespace as opposed to creating a net new one just for this tutorial.

What's also true is that it may be easier if the customer has an AAM license to create a cross-device data source in AAM just for this tutorial. It'll show up in the identity namespace and then when they delete the namespace on the AAM side after they've finished the tutorial, it will actually delete it from AEP identities as well. That way, the only customers that may need to create a luma identity namespace and have it permanently in their production sandbox will be non-AAM customers going through this tutorial.

Open help/tutorial-web-sdk/configure-identities.md and review Step 2, focusing on the sandbox and identity-namespace guidance. Clarify the paths for customers without AEP or AAM licenses, including existing AAM namespaces and deletion behavior. Done means the tutorial accurately explains which customers should create or reuse a namespace and the permanence of that choice.

Written by the indexing model from the issue text.