Replace node config reference with code generation.

[winder]

With algorand/go-algorand#5729 the node config inline documentation is brought into alignment with the developer portal.

This PR uses the config_json_gen utility to render the node config reference page from the code comments.

[winder]

Converted back to the draft. It doesn't seem to display properly:
https://github.com/algorand/docs/blob/bc19457bd4f5340b8b9b2f57ac756e5665e8cd44/docs/run-a-node/reference/config.md

[winder]

Looks sorta ok now: https://github.com/algorand/docs/blob/2bab6a940df423d86442ed2747422ac8b3ec189b/docs/run-a-node/reference/config.md

[ryanRfox]

looks like it renders properly now. good stuff here

[nullun]

Just came across this after manually updating the page in #1186 🤦

[winder]

Just came across this after manually updating the page in #1186 🤦

Ouch. Did the automation do a good job? How do we get the process updated?

[nullun]

The script works great! This is far better, thanks Will.

I think ultimately we want it to be run as part of the release-checker pr-generator workflow so when a new stable release is made it'll PR any new config.md changes, but I'm not familiar with that process atm.

I'm happy to approve this PR and get it merged in though.

[nullun]

@winder I added a single function to the code to HTML encode the default values, I have also updated the pr-generator to run this on new releases. Look good?

@ryanRfox Could I get you to take a last look to make sure there's nothing obviously wrong?

Then I'll merge.

[winder]

The recent release includes some new data directory configurations. It would be good to wrap up this PR, and run the script again to pull in the new configurations.

cc: @nullun @ryanRfox

[nullun]

Just tested again locally and am all for merging it in. @ryanRfox ?