cache apihost supported runtimes

[shazron]

Right now the supported runtimes are static:

aio-lib-runtime/src/utils.js

Line 24 in 822176f

const SupportedRuntimes = ['nodejs:10', 'nodejs:12', 'nodejs:14']

On first run, cache the supported runtimes in the config, per apihost. There is the utils.getSupportedServerRuntimes function available.

[aiojbot]

JIRA issue created: https://jira.corp.adobe.com/browse/ACNA-1688

[purplecabbage]

I think a better approach is just to wait for the call to fail and present a nice error message telling the user what to do. There should be one source of truth, so we do not need to update the client when the server changes.
Caching values seems like extra code for something that changes infrequently.

[shazron]

We already do what you suggested. This was an enhancement.

[purplecabbage]

The issue still exists, as we first check our local list, and if it is not there we throw ..
after that, we check the server, which very well might allow the version ...

try {
  validateActionRuntime(retAction)
} catch (e) {
  const supportedServerRuntimes = await getSupportedServerRuntimes(apihost)
  throw new Error(`${e.message}. Supported runtimes on ${apihost}: ${supportedServerRuntimes}`)
}

Saw this error today:

Error: Unsupported node version 'nodejs:18' in action amazon-app/bulk-read. Supported versions are 
 ›   nodejs:10,nodejs:12,nodejs:14,nodejs:16. Supported runtimes on https://adobeioruntime.net/: 
 ›   nodejs:16,nodejs:14,nodejs:18,nodejs:12,nodejs:10

Which is still technically happening because they were using the previous version of aio-lib-runtime, but the point is the server said it was fine, and our code still threw.

[shazron]

resolved via #138