Enable easy creation of static index.html pages

[mescanne]

This uses string tokens for the manifest.json and catalog.json data files that can be used as an alternative -- replacing them with actual objects -- of reading in JSON files.

This is a step to resolving #53. An additional PR will be submitted for dbt-core with the generated index.html from this version.

Description

Generating a static index.html after a webpack process is not straightforward.

Two strings are used as a unique value in the generated index.html that can be replaced with objects that, when replaced, will use those object values rather than fetching through HTTP for the data.

This will enable an extra step in dbt-core docs generation to generate a static index.html upon request.

Why? See issue #53 for many users over years expressing desire for this. For example, including the static index.html in a ZIP file -- which can be inspected locally -- and hosting it in a blobstorage/GCS/S3 in a way that can be downloaded in isolation.

Checklist

• I have read the contributing guide and understand what's expected of me
• I have signed the CLA
• I have run this code in development and it appears to resolve the stated issue
• I have opened an issue to add/update docs, or docs changes are not required/relevant for this PR
• I have run changie new to create a changelog entry

[mescanne]

NOTE:

• I also removed the TARGET_PATH (not being used)
• I had to use --openssl-legacy-provider due to nodejs 17 (see this)

[QMalcolm]

Looks great! Thanks again for doing this work 🙂