The redirect was going to a non-existent URL when viewed on the deployed
docs.

This was happening because the absolute paths `/api/whatever` don't
exist in the deployed
site -- it's actually `/en/latest/api/whatever`. This went unnoticed
because it works
locally (where there is no /en/latest prefix).

To fix, use a relative url (relative urls are relative to the path that
is redirected from)

This basically allows using any python-build-standalone archive and
using it
if custom flags are set. This is done through the
`single_version_platform_override()`
API, because such archives are inherently version and platform specific.

Key changes:
* The `platform` arg can be any value (mostly; it ends up in repo names)
* Added `target_compatible_with` and `target_settings` args, which
become the
  settings used on the generated toolchain() definition.

The platform settings are version specific, i.e. the key
`(python_version, platform)`
is what maps to the TCW/TS values.

If an existing platform is used, it'll override the defaults that
normally come
from the PLATFORMS global for the particular version. If a new platform
is used,
it creates a new platform entry with those settings.

Along the way:
* Added various docs about internal variables so they're easier to grok
at a glance.

Work towards #2081