Future of vspec2aaproperties (branch code_generation) and other branches

As of today we have a half finished (?) tool vspec2aaproperties in branch `code_generation`. We also have some issued related to it, like #145 and #148

Some thoughts:
- Is it likely that anyone will contribute something more to this branch?
- Is it worth saving?
- How shall we document the branches we have, i.e. purpose and content? In the wiki? We have some other branches (see below) that are not actively used. What is our policy for keeping them?

If we want to keep it I would suggest renaming it, as the current name `code_generation` does not really say much about the content/intent. Something like `feature/vspec2aaproperties` would make more sense, or if we want to create an issue to track the work and call the branch `issue/` or similar. I assume that we also in the future now and then might need temporary collaboration branches, so having a naming standard could make sense.

https://github.com/COVESA/vss-tools/tree/serialization
https://github.com/COVESA/vss-tools/tree/temp_csv2pdf_test_branch

(@gunnarx - you maybe know the history/status of the branches above)

Start by reviewing issues #145 and #148 and the linked `code_generation`, `serialization`, and `temp_csv2pdf_test_branch` branches to understand their status and purpose. Done means reaching a decision on whether to retain the branches, documenting their purpose and content, and recording a branch-naming and retention policy.

Written by the indexing model from the issue text.