Proposal repos: keep generating markdown?

The WASI subgroup maintains the wit-abi-up-to-date Github Action for checking that the wit in a proposal is valid, and that the markdown files in the proposal match the wit.

Mechanically validating the wit documents is a vital part of CI. However, keeping the rendered markdown up to date with changes in the wit creates a burden for contributors and maintainers.

In my informal survey so far, I haven't heard feedback from anyone who actually appreciates and uses the rendered markdown. I have heard feedback from numerous proposal authors and contributors that the rendered markdown creates significant inconvenience. Since the markdown is a direct transform of the wit, we could find a different way to make it available to those who use it (if they exist), e.g. by changing the action to generate markdown and publish it to github pages, or something along those lines.

I'd like to collect more feedback here, with the predisposition to stop generating markdown unless we hear from people who are really using it.

For an example of the rendered markdown, see: https://github.com/WebAssembly/wasi-filesystem/blob/main/imports.md

Review the wit-abi-up-to-date GitHub Action and the wasi-filesystem imports.md example linked in the issue. Read the existing feedback, then determine whether contributors use the rendered markdown and whether it should continue being generated or be published another way. Done looks like a documented project decision with an agreed direction.