Individual component versioning through tag prefixes

[srprash]

MinVer provides a feature to version multiple projects in a single repo independently by defining a tag prefix for each project. I believe we can leverage this feature by defining specific tag prefix for each project and then creating a tag with <projectPrefix>-<version> when we want to do a release for the project.

For example, if the project name is OpenTelemetry.Contrib.Extensions.AWSXRay, the tag prefix will be Extensions.AWSXRay- and the tag name will be Extensions.AWSXRay-1.0.0-rc2.

Any new project added to the repo must define the <MinVerTagPrefix> in its csproj file.

I checked the naming requirements for a git tag name but didn't find a restriction on the length. Please call out here if you know of any such limit.

[codecov]

Codecov Report

Merging #63 (12ccd44) into main (a7e698f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #63   +/-   ##
=======================================
  Coverage   70.95%   70.95%           
=======================================
  Files          28       28           
  Lines         809      809           
=======================================
  Hits          574      574           
  Misses        235      235           

[cijothomas]

Thanks! this is the same approach used in the sdk repo as well. So far it works well. :)