Fix release process to not use external config

[Integralist]

The CLI configuration file was being pulled down from a Fastly endpoint that handled the construction of the config (this was because an internal Fastly service already had access to all the starter kit data that was injected into the config for the CLI to consume).

This caused issues with the CLI release process as the person cutting the release might not have waited for the internal system to have run its daily cron that updated the configuration data.

To avoid this race condition we've moved all this logic inside of the CLI's own CI process.

[Integralist]

Just some comments for the reviewer...

[triblondon]

When we chatted about this on zoom, the approach we discussed was to list SK repo URLs in a file in the CLI repo, and then pull the title and description of the SKs from the SK repo's fastly.toml file during the CLI build. It seems like the solution here is to bake the title and description data into the CLI repo directly, which duplicates and disconnects it from the SK's canonical data.

My concern is that this creates a maintenance overhead, and an unexpected gotcha if you update the SK and then expect the output from the CLI to change.

These are the repos I think we should offer in the CLI, in this order:

• Rust:
  • https://github.com/fastly/compute-starter-kit-rust-default
  • https://github.com/fastly/compute-starter-kit-rust-empty
  • https://github.com/fastly/compute-starter-kit-rust-static-content
  • https://github.com/fastly/compute-starter-kit-rust-websockets
• JavaScript
  • https://github.com/fastly/compute-starter-kit-javascript-default
  • https://github.com/fastly/compute-starter-kit-javascript-empty
• AssemblyScript
  • https://github.com/fastly/compute-starter-kit-assemblyscript-default
• Go
  • https://github.com/fastly/compute-starter-kit-go-default

Could we use that approach, and store only the URLs here in the CLI - adding the other data when the CLI is built?

[Integralist]

@triblondon here's the script for generating the config.

[fgsch]

LGTM, windows CI failure aside :)