[auto-release-pipeline] update auto-calculation rule for version number

[msyyc]

strategy about package version for SDK (track2)
After discussion, we summarize the version principle:
(1) For single api, as long as the current tag is preview, the package version should be preview(for example, preview package version for python is x.x.xbx)
(2) For multi api, there will be default api-version if customers don't assign api-version. As long as default api-version is preview, then the package version is preview.
(note: If the name of tag contains 'preview' or the tag contains files of 'preview' folder, then the tag is preview tag.)
(note: If the api-version contains 'preview', then it is preview api-version.)

test link:
#19492
#19491
#19489

[check-enforcer]

This pull request is protected by Check Enforcer.

What is Check Enforcer?

Check Enforcer helps ensure all pull requests are covered by at least one check-run (typically an Azure Pipeline). When all check-runs associated with this pull request pass then Check Enforcer itself will pass.

Why am I getting this message?

You are getting this message because Check Enforcer did not detect any check-runs being associated with this pull request within five minutes. This may indicate that your pull request is not covered by any pipelines and so Check Enforcer is correctly blocking the pull request being merged.

What should I do now?

If the check-enforcer check-run is not passing and all other check-runs associated with this PR are passing (excluding license-cla) then you could try telling Check Enforcer to evaluate your pull request again. You can do this by adding a comment to this pull request as follows:
/check-enforcer evaluate
Typically evaulation only takes a few seconds. If you know that your pull request is not covered by a pipeline and this is expected you can override Check Enforcer using the following command:
/check-enforcer override
Note that using the override command triggers alerts so that follow-up investigations can occur (PRs still need to be approved as normal).

What if I am onboarding a new service?

Often, new services do not have validation pipelines associated with them, in order to bootstrap pipelines for a new service, you can issue the following command as a pull request comment:
/azp run prepare-pipelines
This will run a pipeline that analyzes the source tree and creates the pipelines necessary to build and validate your pull request. Once the pipeline has been created you can trigger the pipeline using the following comment:
/azp run python - [service] - ci

[msyyc]

/check-enforcer override