[Fix] SDK Versioning strategy update

[brapoprod]

This PR updates the SDK versioning strategy by working with buildnumber pre-releases and bumps the minor version on release

PR Guidelines

• I have read the contribution and PR guidelines

[github-actions]

Coverage Report

Coverage report can be checked at https://stgrafxstudiodevpublic.blob.core.windows.net/sdk/coverage/487/coverage.html

Use PR sdk package

Tarball can be downloaded from https://stgrafxstudiodevpublic.blob.core.windows.net/sdk/dev-packages/487/studio-sdk.tgz

To use in local project, change package.json to use local tarball

"dependencies": {
    "@chili-publish/studio-sdk": "https://stgrafxstudiodevpublic.blob.core.windows.net/sdk/dev-packages/487/studio-sdk.tgz"
}

[github-actions]

Unit Test Results

    1 files    36 suites   38s ⏱️
369 tests 369 ✔️ 0 💤 0 ❌
379 runs  379 ✔️ 0 💤 0 ❌

Results for commit bd147b4.

♻️ This comment has been updated with latest results.

[pietervp]

Summary of PR:

PR Merging

When a pull request is merged, the build version is bumped to a new prerelease version (e.g., 1.0.1-0). (https://github.com/chili-publish/studio-sdk/pull/487/files#diff-8bda6d2a89c0f63ae4a26d4f92749f6acd9dc29ecfcb0c673c03093fb601c466R39)

Release Tagging

When a release is tagged, the prerelease suffix is removed, and the version is set accordingly.
The packages are published to npm with both the stripped tag and the latest tag. (https://github.com/chili-publish/studio-sdk/pull/487/files#diff-c1706e92640d674460bf554d0ca1d2b918d6f55c6609faf789a914048fbe0cdcR44-R46)

Post-Release Version Bump

After the release, the minor version is automatically incremented to the next prerelease version (e.g., 1.1.0-0).
Version numbers across the repository are aligned and committed. (https://github.com/chili-publish/studio-sdk/pull/487/files#diff-c1706e92640d674460bf554d0ca1d2b918d6f55c6609faf789a914048fbe0cdcR75-R87)

Looks good to me!