Clarify: versioning

Versioning of individual "elements" is required for [requirements only](https://eclipse-score.github.io/process_description//main/process_areas/requirements_engineering/guidance/requirements_process_reqs.html#gd_req__req_attr_version). Is that correct?

Todays implementation forces all elements to have a `version`, which does not match the process requirement.

Especially this does not make a lot of sense for automatically generated reports like the [module verification report](https://eclipse-score.github.io/module_template/main/verification_report/module_verification_report.html)? As the report is assembled on the fly, and no diff appears in reviews, there is nothing that can be reviewed within a review. As the report includes pretty much everything in a specific repository, every change leads to a version increase?

Start by reading the linked requirements-engineering guidance and the module verification report documentation, then compare their versioning expectations with the current process description. Done means the documentation clearly states which elements require versions and how automatically generated reports are handled.

Written by the indexing model from the issue text.