How to handle survey-specific code?

Currently, `results` uses a lot of survey-specific code (components, configs, etc.) which is all imported using webpack alias. But that means it has to live in `monorepo` instead of `surveys`.

Config such as colors, etc. could potentially be made available through the API (even though this is not always ideal since it's more work compared to just `import`ing; and also it's harder to ensure proper types), but that doesn't work for components such as a survey's animated logo.

Is there a way to `import` from the `survey` repo based on the currently active `editionId` in `results`'s `.env` file?

Start by tracing how results imports survey-specific components and configs through the webpack aliases, then inspect how the active editionId is supplied in results' .env file. Compare the stated API approach with the need to import components such as an animated logo. Done means an agreed, documented architecture for loading survey-specific code from surveys without leaving it in monorepo.

Written by the indexing model from the issue text.