workflow automate semantic built version to streamline release management

[dean-taylor]

Is your feature request related to a problem? Please describe.

During automated build process a check late in the instructions fails if a release carrying the same version is present. An overwrite of the release is not appropriate as there may be deployments using the released image and the re would be a slight chance of altering functionality or user experience without appropriate release.

Describe the solution you'd like

Only the major, minor and patch components are continued as part of the code versioning and the build portion of the semantic version becomes part of the automated build workflow. The build is to be an incrementing index, reset to 0 when any change to the higher order numbers is submitted.
This provides a numbering process that is not overly complex to implement, is understood by most client applications for selection of image or chart variants and removes a common block in the automated build and release process.

Describe alternatives you've considered

Keep the full version number in the code and ensure the process of incrementing becomes part of the Pull request verification process. This check could be added to the submission of pull requests to fail if version number already exists, however does not cater for multiple pull requests over short periods which would become more common as the work on the project escalates.

Additional context

No response