Migrate docs.rapids.ai into rapids.ai framework

[exactlyallan]

Based on proposal - https://docs.google.com/presentation/d/1-N1f5JJArDzcMdxveoJtKeziz0hldBdTtL2wvY6DiqM/edit#slide=id.p

Tasks

Preview Give feedback

1. Push doxygen docs to build into sphinx with breathe @ajschmidt8 to assist
2. Create external RAPIDS theme based on PyData Theme + Nav @jacobtomlinson and @exactlyallan Create RAPIDS Sphinx Theme #379
3. Create docs style and content guide - @exactlyallan
4. Migrate Quasi-docs (I.E. viz guide) from Jekyll into Hugo in Rapids.ai @exactlyallan
5. Setup domain forwarding and check S3 dir structure
6. Migrate content from rapidsai/docs to rapidsai/rapids.ai rapids.ai#346
   +0

[ajschmidt8]

There are some additional backend changes that I'm working with @AyodeAwe on to enable this migration.

Namely setting up a CloudFront Distribution in front of the S3 bucket that has all of the docs and enabling Netlify's proxy feature to work correctly with that CloudFront Distribution.

We're also brainstorming on ways to enable PR previews for docs builds so that the individual repos (e.g. cudf, cuml, etc) can see what their doc changes look like before merging PRs.

[ajschmidt8]

@exactlyallan, quick side note. We should also try to move the viz guide to S3 and use proxying for that too since the JSON files are relatively large.

I think the last time I checked, they were contributing around ~100MB to the git history for the docs repository.

[jacobtomlinson]

We're also brainstorming on ways to enable PR previews for docs builds so that the individual repos (e.g. cudf, cuml, etc) can see what their doc changes look like before merging PRs.

We have Read the Docs enabled on the deployment repo, just for the PR previews. In the Dask Blog we use Netlify for previews. In both cases neither actually gets deployed to the service that provides the previews.

[exactlyallan]

Note: Merged PR kicks off GHA to build docs and push to S3 bucket with version folder i.e. https://d1664dvumjb44w.cloudfront.net/cudf/23.04/html/