Remove cloudtest notifications sent to lowdev

[OneBlue]

Summary of the Pull Request

PR Checklist

• Closes: Link to issue #xxx
• Communication: I've discussed this with core contributors already. If work hasn't been agreed, this work might be rejected
• Tests: Added/updated if needed and all pass
• Localization: All end user facing strings can be localized
• Dev docs: Added/updated if needed
• Documentation updated: If checked, please file a pull request on our docs repo and link it here: #xxx

Detailed Description of the Pull Request / Additional comments

Validation Steps Performed

[Copilot]

Pull request overview

This PR updates the Azure Pipelines CloudTest job configuration to stop attributing scheduled build requests to the "lowdev" alias, aligning notifications/requester identity with the actual build requester.

Changes:

• Removed scheduleBuildRequesterAlias: "lowdev" from the CloudTestServerBuildTask inputs.
• Kept notificationSubscribers set to $(Build.RequestedForEmail) so notifications go to the requesting user.

[Copilot]

Pull request overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.

[Copilot]

Pull request overview

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

[Copilot]

This step logs $(Build.RequestedForEmail) directly into build logs. Email addresses are PII and can end up retained/shared beyond the original audience of the notification. If the intent is troubleshooting, consider removing this log or masking the value (e.g., log only the domain or a hashed/obfuscated form), or use a non-PII identifier instead.

Suggested change

	- script: echo "Build requested for email - $(Build.RequestedForEmail)"
	displayName: "Log build requested for email"
	- script: echo "Build requested for - $(Build.RequestedFor)"
	displayName: "Log build requested for user"

[benhillis]

Hey @OneBlue 👋 — Following up on this draft PR. CI is green, but there's 1 unresolved review thread about a PII concern — \\\ being logged in the pipeline. Could you take a look at that? Is this draft still planned for merge?