Description of change
This feature is to reflect to juju user another attribute(charm-version) that remain unchanged if the same charm is deployed on the model.
This PR addresses code changes for writing the version details from charm manifest(version file) into the Database and display the version details in juju status.
QA steps
As for this PR is concerned, the user can deploy a local charm with a version file manually written containing the output of 'git describe --dirty' command. The complex logic of how its handled in different scenarios is going to be addressed in another PR.
The tabular form of status is displays the trimmed part of the version details. The yams and son has complete details of version from the charm manifest.
Documentation changes
Yes. juju status needs to get updated on the additional information that gets displayed plus how it is going to be in different format.
该提问来源于开源项目：juju/juju
