Move code for document/minute generation to another branch

[coolharsh55]

Remove the code folder from the main and dev branches and put it in another branch (e.g. docgen) so that it doesn't get bundled in the releases zip and it would also help commits and PRs not manipulate both code and data at the same time.

E.g. workflows:

• clone the git repo in two locations, one for main called dpv and one for docgen called dpv-docgen. Modify the output path for code run in dpv-docgen to generate outputs in ../dpv (separate git repo) so the two git commit histories are easier to manage.
• when concept/documentation changes: make changes to dpv-docgen as many times as needed. When okay to publish, produce outputs in ../dpv and add a commit there for the outputs.
• changes to code won't modify the history of DPV (specification), so we will have a 'clean' history only for the additions/modifications of the DPV and extensions
• PRs changing main can be discouraged (easier management for release history) and instead, they can be for dpv-docgen branch for any code changes. Direct modification of CSVs should be discouraged.