Add pre-release support to update workflow

[masesdevelopers]

Description

Introduce optional inputs PreReleaseCurrentVersion and PreReleaseNewVersion and update all file replacement steps to include pre-release tags. Files updated: Common.props, .nuspec, .psd1 and .csproj replacements now concatenate the pre-release values when present, and the generated commit/PR title and message also include the pre-release tags. This enables updating stable and pre-release versions in the same workflow.

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

• My code follows the code style of this project.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have read the CONTRIBUTING document.
• I have added tests to cover my changes.
• All new and existing tests passed.