Consider adapting SolrWayback for public use

[anjackson]

Beyond internal access, to use SolrWayback as a public service (replacing the faceted search part of ukwa-ui), we need to consider more complex issues:

• Add localization support: UI internationalization netarchivesuite/solrwayback#23
• Implement as an accessible, responsive design, e.g. follow Warclight Bootstrap for basic facet design and UI. Consider TailwindCSS for layout with Shoelaces for components, to be consistent with Webrecorder's work.
• Pages like the Toolbox etc. should also be routed and bookmarkable.
• Display an error message in the UI when calls the the back-end fail, rather than appearing to still be busy.
• Security review - make sure all APIs can safely be made public.

As well as some minor changes:

• Make sure the indexer config default (and in SolrWayback Docker Compose) uses url_norm.
• Add support for common deployment context headers (X-Forwarded-Proto, X-Forwarded-Host etc.) to SolrWayback, so hardcoding the base URL is no longer necessary.
• Possible optimisation: Change ArcHTTPResolver to check response for Content-Bytes rather than make two requests per request (where the first probes for Accept-Ranges: bytes (Or at least only check the first time?)

This needs to be weighed up against the difficulties in adapting the off-the-shelf options.

[anjackson]

Just noticed that some parts are weird, because facets with counts of 0 are being returned.

• Set facet.mincount=1 ukwa/solrwayback@fafd2f4