[Fleet]Start Fleet Server Command under Add Agent is not getting formatted correctly in PowerShell

[ghost]

Describe the bug
Start Fleet Server Command under Add Agent is not getting formatted correctly in PowerShell.

Build Details:

version: 7.14.0-BC1
Commit:071a74e02f82b79a4a10026b5c9e02d593112fd4
Build:42292

Browser Details:
N/A

Browser Details
All

Preconditions
1.Kibana users should be logged in.

Steps to Reproduce
1.Go to Integrations.
2.Search for System integration.
3.Click on add Agent .
4.Fill in all required details.
5.Observed that fleet server command copied from kibana is not formated and could not run in PS.

.\elastic-agent.exe install  -f \
 --fleet-server-es=https://be416f94b3c94529a80af38190153823.europe-west1.gcp.cloud.es.io:443 \
 --fleet-server-service-token=AAEAAWVsYXN0aWMvZmxlZXQtc2VydmVyL3Rva2VuLTE2MjU0NjQ0ODc3MTY6VTdBUjZHLXVSc2llZUJnanQwUklNUQ \
  --fleet-server-policy=policy-elastic-agent-on-cloud

Actual Result
Start Fleet Server Command under Add Agent is not getting formatted correctly in PowerShell.

Expected Result
Copied Fleet Server Command could not run in PS

Whats Working

• N/A

Whats Not Working

• N/A

Screen-Shoot

logs

• N/A

[elasticmachine]

Pinging @elastic/security-solution (Team: SecuritySolution)

[elasticmachine]

Pinging @elastic/fleet (Team:Fleet)

[manishgupta-qasource]

Reviewed & Assigned to @jen-huang

CC @EricDavisX

[dikshachauhan-qasource]

Hi @jen-huang

We have observed that Add agent issue having on-prem instruction to set fleet server up is displayed on staging, Production and cloud-qa environments as first raised under #103550 (comment).

FYI
Observations on Prod/staging env:

• No default Fleet-server agent is installed under 'elastic agent cloud policy'.
• 'Edit deployment' message is displayed on Fleet agents tab and under 'Enroll in Fleet' fly out.
  
• On navigating to Add agent flyout under integrations tab, we are able access instructions to create a self-managed fleet-server.
• However, instructions shown up here are related set up fleet server on self managed environment.
• Further, on scrolling down, we observed above reported issue having in-correct commands format for installing fleet-server agents. [Point 5 is observed on all the deployments: Cloud-qa, staging and production].

Observations on Cloud-qa env:

• Default Fleet-server agent is installed under 'elastic agent cloud policy'.
• However, if user creates a user defined policy having fleet-server integration, then On-prem Instructions for setting fleet-server displayed. Reported same issue at [Fleet] On-prem Instructions for setting fleet-server displayed under add agent flyout on cloud deployments #104280.
• Further, on accessing add agent fly-out from Fleet server integration's> policies tab. We are unable to fetch instruction to set-up a fleet-server on cloud. Reported issue at: https://github.com/elastic/fleet-server/issues/519

Please let us know in case on any queries.

Thanks
QAS

[nchaulet]

Looks like the new line character we use on unix \ is not supported in powershell looks like it should be done with a backtick.