Automatically generate protocol contract documentation

[aiman]

Currently, the protocol contract documentation is maintained manually. However, this is not ideal because it can get out of sync with changes in the code base, and there is delayed feedback for the development team. It would be better if the docs are automatically generated from the Solidity source files directly. The source already contains a significant amount of documentation in the NatSpec format, but it is not used for rendering the docs.

The preliminary goal is to deliver:

• scripts that extract the NatSpec data from AGC Solidity code for subsequent use
• scripts (or Quarto extensions) and styling to render the extracted data in the Quarto site

[aiman]

To achieve this with current repo workflow, we'll either need:

• (A) generic feature flag mechanism, ideally with our own top-level config, disadvantage being having to implement Quarto filters to achieve this
• (B) document to track what feature flags are available to be toggle, disadvantage being changes can be quite extensive and deep in CSS files, increased scope for errors

My view on (A) is that we'd have a single top-level yaml/toml config, or reuse a Quarto one, and define our feature flags in there. And then rely on custom filters/scripts to propagate those flags in the right places, e.g. CSS class or hiding documents (draft: true/false).