Publish channel.json

[braver]

Original discussion: packagecontrol/the-packages-site#18 (comment)

• The channel.json should be available at a URL under the site's public URL (ie. not a GitHub build asset URL)
• The URL should be visible on the site so people can know where to find it easily *
• The ST3 channel should also be discoverable

*) Especially for the time being where we're not actively switching users to the new channel yet

[kaste]

I think this should be a small page like a README. Links to the final channel files, in the two variants. Plus links to the releases where we pull it from. The releases page itself now link to the action logs. Which link to the action code/definition. Open and friendly.

[braver]

@kaste think we can pass the channel and workspace files as build artefacts to the gh-pages job? Ie. instead of downloading with curl?

[FichteFoll]

pass the channel and workspace files as build artefacts to the gh-pages job? Ie. instead of downloading with curl?

Note that the requirement for this is that the website must be buildable without a crawler run and I'm not sure an action can refer to artifacts of a(ny) previous action run. Or the crawler must have a no-op mode where it skips crawling to not run into API limits when the website is built too frequently.

[braver]

Note that the requirement for this is that the website must be buildable without a crawler run

Oh, yeah.. blame the heat 😅 No that won't work. Curl it is then.

[braver]

Handled via #47