Capture Airnode gateway URLs programmatically

[dcroote]

Gateway URLs are printed to the console at the end of a cloud deployment as described in the docs here. The URLs aren't easily retrievable otherwise.

To facilitate #1858, #1904, and #1786 (because airnode-client is used in gateway E2E tests) there should be a helper function to capture these URLs.

[bbenligiray]

I suppose it wouldn't be easy to mock a heartbeat server for this

[dcroote]

The heartbeat is an interesting thought. It turns out it was pretty easy to do in #1904 with a simple regex against the deployment command output logged to the console:

airnode/scripts/test-release.ts

Lines 59 to 74 in 3a05d77

	export const extractGatewayUrls = (consoleOutput: string) => {
	const httpRegex = /HTTP gateway URL: (https:\/\/[^\s]+)/;
	const httpMatches = consoleOutput.match(httpRegex);
	if (!httpMatches) {
	throw new Error('Could not extract the HTTP gateway URL from console output');
	}
	const signedRegex = /HTTP signed data gateway URL: (https:\/\/[^\s]+)/;
	const signedMatches = consoleOutput.match(signedRegex);
	if (!signedMatches) {
	throw new Error('Could not extract the HTTP signed data gateway URL from console output');
	}
	return {
	httpGatewayUrl: httpMatches[1],
	signedHttpGatewayUrl: signedMatches[1],
	};
	};

[dcroote]

Closing as the regexs work well