feat: multi step api runner

[shahzad31]

multi step api runner

can be tested with

import { apiJourney, monitor, step } from '@elastic/synthetics';

apiJourney(`My Example api journey`, ({ request }) => {
  monitor.use({
    enabled: true,
  });
  step('launch application', async () => {
    const req = await request.get('https://api.restful-api.dev/objects');
    console.log(await req.json());
  });
  step('go to url', async () => {
    const req = await request.get('https://example.badssl.com/');
    console.log(await req.json());
  });
});

[emilioalvap]

Suggested change

	return await Promise.all(promises);
	return await Promise.allSettled(promises);

Accounting for unrelated rejections

[vigneshshanmugam]

Ideally I would like us to have a base Journey class that both BrowserJourney and APIJourney extends from and the runner should be a single entity that decides how to run each of them. I am not in favor of having multiple runners.

[vigneshshanmugam]

Did a first pass.

[vigneshshanmugam]

browserDelay is not appropriate for apijourneys?

[vigneshshanmugam]

This feels a bit weird , Maybe a better way would be to check if there are defined browser journeys and then launch the browser context etc based on that.

[vigneshshanmugam]

can it have a Driver at any point?

[vigneshshanmugam]

This needs some careful review as we need some extensive tests for cached, aborted, intercepted requests etc, Will do a detailed review later on when we have tests etc.

[vigneshshanmugam]

Plugin Manager should be transparent to the underlying journey that was run whether its browser/api based. There will be always a chance when browser/api based journeys coexisting. I would handle these and make them respective plugins transparent.