🩹 [Patch]: Name the helper module after the action (Resolve-PSModuleVersion.Helpers) (#8)

Aligns the helper module with the action helper-module naming standard:
name it after the action (`Resolve-PSModuleVersion.Helpers`) instead of
a generic name.

PR #4 introduced the interim name `ResolveVersion` to fix the `Helpers`
collision; this brings it to the ecosystem-wide convention
(`<Action>.Helpers`) now that the standard is in place.

## Changes

- `scripts/ResolveVersion.psm1` →
`scripts/Resolve-PSModuleVersion.Helpers.psm1`
- `tests/ResolveVersion.Tests.ps1` →
`tests/Resolve-PSModuleVersion.Helpers.Tests.ps1`
- `tests/ResolveVersion.Tests.Data.psd1` →
`tests/Resolve-PSModuleVersion.Helpers.Tests.Data.psd1`
- Updated the entry-script import (`scripts/main.ps1`), the test module
import, the test data-file path, and the two `Mock -ModuleName`
references. Kept the framework `Import-Module -Name 'Helpers'`.

No runtime logic changed (100% file rename + reference updates).

## Validation

Tests pass 131/131 under a simulated `Helpers` name collision (a second
module named `Helpers` loaded before Invoke-Pester). PSScriptAnalyzer
clean apart from the pre-existing `PSAvoidUsingWriteHost` warnings
(unchanged module body).

Part of PSModule/Process-PSModule#364. Standard: the "Name helper
modules after the action" rule in the GitHub Actions coding standard
(MSXOrg/docs#24).

Author: MariusStorhaug

scripts/ResolveVersion.psm1 …pts/Resolve-PSModuleVersion.Helpers.psm1scripts/ResolveVersion.psm1 renamed to scripts/Resolve-PSModuleVersion.Helpers.psm1 scripts/ResolveVersion.psm1 renamed to scripts/Resolve-PSModuleVersion.Helpers.psm1

@@ -4,7 +4,7 @@ param()
 $PSStyle.OutputRendering = 'Ansi'
 
 Import-Module -Name 'Helpers' -Force
-Import-Module -Name "$PSScriptRoot/ResolveVersion.psm1" -Force
+Import-Module -Name "$PSScriptRoot/Resolve-PSModuleVersion.Helpers.psm1" -Force
 
 $actionInput = Read-ActionInput
 $config = Get-PublishConfiguration -SettingsJson $actionInput.SettingsJson

scripts/main.ps1

@@ -9,7 +9,7 @@
 param()
 
 # Load test data at script scope so it is available during Pester discovery (-ForEach)
-$TestData = Import-PowerShellDataFile -Path "$PSScriptRoot/ResolveVersion.Tests.Data.psd1"
+$TestData = Import-PowerShellDataFile -Path "$PSScriptRoot/Resolve-PSModuleVersion.Helpers.Tests.Data.psd1"
 
 BeforeAll {
     # Install PSSemVer for version handling
@@ -25,7 +25,7 @@ BeforeAll {
     }
 
     # Import the module under test
-    Import-Module -Name "$PSScriptRoot/../scripts/ResolveVersion.psm1" -Force
+    Import-Module -Name "$PSScriptRoot/../scripts/Resolve-PSModuleVersion.Helpers.psm1" -Force
 }
 
 Describe 'Resolve-ReleaseDecision' {
@@ -92,7 +92,7 @@ Describe 'Resolve-ReleaseDecision' {
 
 Describe 'Get-NextModuleVersion' {
     BeforeAll {
-        Mock -CommandName Find-PSResource -ModuleName ResolveVersion -MockWith { @() }
+        Mock -CommandName Find-PSResource -ModuleName 'Resolve-PSModuleVersion.Helpers' -MockWith { @() }
         $emptyReleases = @([PSCustomObject]@{ tagName = 'v0.0.0'; isLatest = $false; isPrerelease = $false })
     }
 
@@ -133,7 +133,7 @@ Describe 'Get-NextModuleVersion' {
 
 Describe 'End-to-end: Resolve-ReleaseDecision + Get-NextModuleVersion' {
     BeforeAll {
-        Mock -CommandName Find-PSResource -ModuleName ResolveVersion -MockWith { @() }
+        Mock -CommandName Find-PSResource -ModuleName 'Resolve-PSModuleVersion.Helpers' -MockWith { @() }
         $emptyReleases = @([PSCustomObject]@{ tagName = 'v0.0.0'; isLatest = $false; isPrerelease = $false })
     }