Adopt end-host autoconfiguration into official end-host stack

[jiceatscion]

As per the last TC impl meeting, this task is first on the "Usability" track and François has agreed to take the lead.

[jiceatscion]

A couple of points that have been recorded from the last discussion:

• The various pieces are scattered between ETH netsec and Magdeburg ovgu repos. Both groups need to be involved.
• It is used by JPAN. May be the go pan API could do the same.
• Anapaya is interested in the topic too (esp. fetching TRCs). However, will not productize anything that relies on topology.json.
• Dominik to provide feedback on bootstraper in public repository.

[jiceatscion]

This is closely related to other configuration topics. It would be good to have a coherent framework that allows an AS
to:

• Describe its topology
• Configure its routers accordingly
• propagate the relevant information to end-hosts
• Stop relying on unspecified ad-hoc config file schemas

[martenwallewein]

Hey all, great to see that this is on the roadmap (or will be)!

Just some related links for this:

• SCION Orchestrator Thats the tooling we use right now to run endhost stacks. Is quite progressed to run on different platforms (Windows, MacOS, Linux) and is recent in development. It also supports the AS site, e.g. built-in bootstrap server
• Endhost Bootstrapper Endhost bootstrapping over various mechanisms.

Note: The orchestrator makes use of functionalities of the bootstrapper, but so far not all (some need to be adapted to compile on Windows) but the long-term goal is to fully include the bootstrapper there.

It would be great to integrate these efforts that we did so far into the new framework!