Suggested Target Updates

Issue in ./help/tutorial-web-sdk/setup-target.md

1. In step 3 where you get the pre-hiding snippet, it would be helpful to include a quick comment about needing to scroll down to find the pre-hiding snippet.
2. In this exercise, we are using the mbox3rdPartyID instead of the identity map. I'd recommend we move to identity map so that it's consistent with the rest of the exercises. Target should be able to use identity map to get AAM segments now per https://jira.corp.adobe.com/browse/PLATIR-23393.
3. The screenshot after step 9 in the first Validate with the Debugger section needs to be updated. The value of eventType is now decisioning.propositionDisplay instead of just "display", which is what's in the screenshot.
4. I think a note about how additional custom scopes fire off additional Target calls would be worth mentioning
5. when going through this, I found it mentally challenging that both the VC and Form editor used the same text "Be active with style". So many of the images are the same, that it took me a few minutes to determine if 1) I really had deactivated my last test and 2) if the form composer was working. While I can certainly see the value in keep the same text across both types of Target activities, I do wonder if we can save some confusion and time by using different text.
6. The screenshots of the debugger in the section for validating the form-based Target activity are screenshots that include the default scope instead of the homepage-hero scope.

Start with ./help/tutorial-web-sdk/setup-target.md and review step 3, the first Validate with the Debugger section, and the form-based Target validation section. Check the identity-map guidance, custom-scope note, activity wording, and all referenced screenshots against the issue details. Done means the tutorial explains the requested behavior and its screenshots show the current eventType and homepage-hero scope.

Written by the indexing model from the issue text.