feat: abort push on duplicate monitors

[vigneshshanmugam]

• fix Duplicate journey id, silently groups synthetic pings under the last journey in list #442
• Aborts the push command if any of the monitors contain duplicate ids with a clean error message and also linking users to the duplicate monitor files where required.
• Decided to handle the logic here as Kibana currently does not have any way to know if there are any duplicates without looking up the saved objects which is not performant when we have all the list already available via the agent.

Testing.

• Build the local project using - npm run build

2. Setup a brand new Synthetics project - node dist/cli.js init [optional-dir]
3. Change the monitior ids for some of the monitors.
4. Run push command - node dist/cli.js push --auth <>

[apmmachine]

💚 Build Succeeded

the below badges are clickable and redirect to their specific view in the CI or DOCS

Expand to view the summary

Build stats

• Start Time: 2022-08-02T17:48:37.685+0000

• Duration: 14 min 52 sec

Test stats 🧪

Test	Results
Failed	0
Passed	172
Skipped	2
Total	174

🤖 GitHub comments

To re-run your PR in the CI, just comment with:

• /test : Re-trigger the build.

[dominiqueclarke]

Since names are used as ids in the absense of id, can we add two monitors with the same name to this fixture as well?

[vigneshshanmugam]

Oh good callout, sure will do.

[vigneshshanmugam]

Done - 4b3837a

[dominiqueclarke]

LGTM, tested four scenarios

1. Two monitors with the same id configured via monitor.use
2. Two monitors with the same id configure via journey options
3. Two monitors with the same name without id configured via the other two options
4. Two monitors, one with an id specified, one without an id specified, where the name of the former and the id of the latter are the same.