feat: Support scope in alias requests

[rmi22186]

Background

Per our updated docs, alias requests support a parameter scope, which was only partially implemented in the web sdk previously. This update supports scope throughout the full SDK, including adding it to the public API tio make it easier for developers to pass it in as opposed to adding it as a property after an alias request is made using our createAliasRequest helper method.

What Has Changed

Add scope throughout alias request code paths, including adding device as default when not provided in order to simplify the code.

Screenshots/Video

• {Include any screenshots or video demonstrating the new feature or fix, if applicable}

Checklist

• I have performed a self-review of my own code.
• I have made corresponding changes to the documentation. - will do as part of another ticket
• I have added tests that prove my fix is effective or that my feature works.
• I have tested this locally.

Additional Notes

• {Any additional information or context relevant to this PR}

Reference Issue (For employees only. Ignore if you are an outside contributor)

• Closes https://go/j/SDKE-695

[sonarqubecloud]

Quality Gate failed

Failed conditions
61.6% Duplication on New Code (required ≤ 3%)

See analysis details on SonarQube Cloud

[jaissica12]

Is there a specific reason for merging this into master instead of development? I believe this should go into development

[rmi22186]

Is there a specific reason for merging this into master instead of development? I believe this should go into development

@jaissica12 - good catch. My mistake!