Remote platforms (WIP!)

[kerberjg]

💖 Allows you to include platforms from remote repos via --remote=<git url>
Also:

• Specify tag/commit: --remote=<git url>#<ref>
• Specify branch: remote=<git url>#heads/<branch>

What this does:

• Clones repository into app/
• Links app/<your repo>/configs/*.json into configs/remote_*.json

This allows you to include your own configs, patches, platforms, apps, plugins, packages without modifying anything! 🥳

Blockers:

• External plugins support (WIP!) toyota-connected/ivi-homescreen#160
• https://github.com/toyota-connected/fluorite/pull/32
• TODO: ivi-homescreen-plugins remove-fluorite & plugin-interface-v2
• TODO: ivi-homescreen-plugins-example plugin-interface-v2

TODOs:

• change ivi-homescreen & ivi-homescreen-plugins branches back to v2.0 after the blockers get merged
• add --remote=https://github.com/toyota-connected/ivi-homescreen-plugins-example to CI to test

[jwinarske]

@kerberjg As a followup to our discussion. The workspace-automation --config option that exists today is intended to use a different configs folder altogether. Oppose to augmenting, you just cherry pick what you want in your local "configs" path, then pass that path in to the upstream flutter_workspace.py. Flutter_workspace.py can be a symlink in your custom configs folder; which is how I did it for AGL; different targets, etc. Removal of patches/configs should happen in an isolated PR. If the feature is blah, then PR should only cover blah.