Increment version for monitor releases

[azure-sdk]

Increment package version after release of azure-opentelemetry-exporter-azure-monitor

[hectorhdzg]

@deyaaeldeen I assume this is an automated process to increase the version for next release, azure pipelines have a requirement for new version to be in the CHANGELOG so this will never pass the checks, would be good to update the automated process used here.

[richardpark-msft]

@deyaaeldeen I assume this is an automated process to increase the version for next release, azure pipelines have a requirement for new version to be in the CHANGELOG so this will never pass the checks, would be good to update the automated process used here.

@praveenkuttappan, to @hectorhdzg 's point above - I was pretty sure the auto-version-updater also inserted a new section into the changelog.md as well when it incremented the version. Is this something @hectorhdzg needs to opt into somehow?

(kind of like this one: #13270)

[deyaaeldeen]

@richardpark-msft @hectorhdzg there is a problem with versioning here which might have to do with the CI failure. This package mixes preview and beta for some reason even though this is not allowed. We have this warning: Version [1.0.0-beta.3] is older than the latestversion [1.0.0-preview.6] in the changelog. Please use a more recent version in the release pipeline here: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=694567&view=logs&j=a1d9647f-8dc0-576b-b75e-f0d4533ebd0e&t=8edb2f73-5db6-5e76-274b-8d5087ebdf9c&l=15.

[ramya-rao-a]

Related: #13210

cc @chidozieononiwu for changelog update question

[weshaggard]

The changelog for this package is in an invalid state. There weren't even any preview.5/6 versions released and we should probably just remove those or merge them with the beta.1 change log. I suspect this might have happened because of the renaming of this package.

[chidozieononiwu]

Manually fixing this with this PR. Am merging preview.5 and preview.6 release notes into beta.1 as @weshaggard suggested. The bug that caused this will be resolved by this PR, there should be no subsequent issues. Apologies for the inconvenience.