chore(docs): update hashes page to pull in code

[TomAFrench]

Description

Problem*

Resolves #4176

Summary*

Additional Context

Documentation*

Check one:

• No documentation needed.
• Documentation included in this PR.
• [Exceptional Case] Documentation to be submitted in a separate PR.

PR Checklist*

• I have tested the changes locally.
• I have formatted the changes with Prettier and/or cargo fmt on default settings.

[github-actions]

🚀 Deployed on https://65b2cfa2575085376aa5cc56--noir-docs.netlify.app

[Savio-Sou]

Thank you @TomAFrench!

Would the use of #include_code work per version when docs are cut into versioned_docs as well?

As in for example if #include_code is used in versioned_docs/version-v0.23.0, would it pull code at v0.23.0's commit instead of from the latest master?

[TomAFrench]

Not perfectly.

The way it works is that on the release PR, we'll generate a version in versioned_docs with the snippets resolved to the code as of the release PR. The markdown is then frozen with the content as of that commit (i.e. we don't codegen for versioned docs after when the version is cut), the links however will still point towards master and so will become stale over time.

We could modify this so that the links point towards the release tag however in future.

[Savio-Sou]

Clarification appreciated. Will make sure to copy content rather than codegen for the retro additions into v0.23.0 in that case.

[signorecello]

Yep those retro additions wouldn't be codegen-ed anyway so the page would look terrible 😊 so it's hard to make a mistake there