Module config does not contain version number

[willprice76]

I have a scenario where I want to use the DXA module concept to define resources and configuration for clientside Javascript applications (little or no .NET/Java code). We would like to be able to control from the CMS which version of the module is being used on the site, and this would most easily be done by exposing the module version number to web application(s).
The template code could easily be updated to ensure that the softwareVersion field from the Module Configuration component is added to the configuration JSON for the module

[rpannekoek]

The given scenario is very specific, but exposing the Module version in published configuration is a good idea in general to help with configuration versioning (if the configuration structure is changed, the new version of the Web App/Module may still be able to work with the old configuration structure; this facilitates rolling upgrades.)

[rpannekoek]

Internal Issue ID (for tracking purposes): CRQ-12803