Better versioning of AsyncAPI.NET packages

[alex-dubrovskyi]

Currently we use a hacky way to sequentially increase version of packages with every workflow run. It's based on GITHUB_RUN_ID which has already exposed one issue - when the value exceeded max int and couldn't be used as part of version number.

The solution would be to steer away from GitHub predefined variables and move to proper semantic versioning.

[github-actions]

Welcome to AsyncAPI.NET. Thank you for reporting your first issue. Please check out our contributors guide.

[xShteff]

@alex-dubrovskyi you can look at https://github.com/LEGO/mould-technology-r-and-d-extensions on how they set it up - the only problem is that their setup doesn't work w/ monorepos/multiple packages.

[VisualBean]

ive fixed this.

[VisualBean]

#27 0.2.<Workflow_Run_Number>.0

[xShteff]

I mean, sure, but what I linked was a rather smart way of generating version numbers based on commits, as well as a changelog :p @VisualBean