Make semver auto create new semver file with correct version info for new branches.

# 🚀 Feature Request

### Relevant Package [**REQUIRED**]

This feature request is for...
edgex-global-pipelines

### Description [**REQUIRED**]
A clear and concise description of the problem or missing capability...
For the Levski patch release (2.3.1), a branch was created on some device service repositories by developers add changes. Those branches immediately will fail their build/CI jobs because there is no semver file for their newly created branch. Someone has to manually go create a file and add correct semver version to it.

### Describe the solution you'd like
If you have a solution in mind, please describe it.
This is open to some discussion, but I think it would be nice for the CI automation to create a new semver file for that new branch. It could use the context of the other semver files on the semver branch to determine which version would be appropriate.

### Describe alternatives you've considered
Have you considered any alternative solutions or workarounds?
Someone has to manually set the proper semver files.