Fetch configs in configuration package build script

[prestwich]

Automatically fetch latest configs from github when building the configs package

Limitations

This may hamper our ability to iterate on configuration layout, as the build.rs will pull in the github version. Can we have some sort of flag to disable the build.rs? 🤔

Conversely, limiting our ability to bork the existing canonical configs is probably a good thing :)

Motivation

Stop having to manually edit configs in this package, allow agents to fetch configs from a canonical source instead of relying on built-in configs

Solution

• build.rs fetches latest development + production + staging configs from github pages
• if the config cannot be fetched, it will be ignored by build.rs. This means past versions in the configs folder will be used
• crate build will fail if a fetched version is unavailable and there is no past version in the folder

PR Checklist

• Added Tests
• Updated Documentation
• Updated CHANGELOG.md for the appropriate package

[luketchang]

Ok given the current setup, iiuc an agent will always take the latest config from github pages. If we do not want to include the latest github pages updates, we can’t actually do anything about it because build will always fetch latest. Clarification on full workflow here and documented in code? :)

[luketchang]

Concluded that lack of flexibility around versions is not problem here. Deploys use pre-deploy folder. GUI shouldn't come before agents