## Description

This pull request includes a small change to the `Publish-PSModule`
function in the `scripts/helpers/Publish-PSModule.ps1` file. The change
modifies the way the `latestPrereleaseNumber` is padded with zeros.

*
[`scripts/helpers/Publish-PSModule.ps1`](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L278-R278):
Changed the `latestPrereleaseNumber` variable to be explicitly cast to a
string before padding it with zeros.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [x] 🪲 [Fix]
- [ ] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [ ] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas

## Description

This pull request includes several changes to the `Publish-PSModule`
script and the `action.yml` configuration file to improve logging.

### Improvements to the `Publish-PSModule` script:

* Added new module dependencies (`Retry`, `GitHub`) to the `#Requires`
statement in `scripts/helpers/Publish-PSModule.ps1`.
* Added `[OutputType([void])]` attribute to the `Publish-PSModule`
function to specify the output type.
* Replaced `Write-Verbose` with `Write-Output` for better visibility of
key process steps and outputs.
[[1]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L162-R192)
[[2]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L199-R221)
[[3]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L240-R246)
[[4]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L282-R301)
[[5]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L308-R323)
[[6]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L332-R345)
[[7]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L363-R376)
* Introduced retry logic using the `Retry` module when fetching the
latest version from PSGallery to handle transient errors.

### Changes to the `action.yml` configuration file:

* Updated the step name from `Run Build-PSModule` to `Run
Publish-PSModule`.
* Simplified the script path reference by removing unnecessary dot
notation.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [ ] 🪲 [Fix]
- [x] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [ ] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas

## Description

This pull request includes several updates and improvements to the
`Publish-PSModule` function in the
`scripts/helpers/Publish-PSModule.ps1` file. The changes focus on
enhancing logging, error handling, and parameter management for
PowerShell Gallery operations.

Enhancements to logging and error handling:

* Added `Write-Output` statements to log the process of finding modules
and prerelease versions in the PowerShell Gallery.
[[1]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9R173-R177)
[[2]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L263-R275)
* Replaced `Write-Output $_` with `throw $_` to improve error handling
during retries.

Parameter management improvements:

* Introduced a hashtable `$params` to manage parameters for the
`Find-PSResource` cmdlet, improving code readability and
maintainability.

Minor corrections:

* Corrected the casing of `Write-GitHubNotice` from `Write-GithubNotice`
to ensure consistent function naming.
[[1]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L335-R347)
[[2]](diffhunk://#diff-780715ac24c6bbe21b54f3d268778136b79f21a62275bbd494dfa857b4ba40d9L376-R388)

Module dependencies:

* Added `PSSemVer` to the list of required modules in the script header.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [ ] 🪲 [Fix]
- [x] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [ ] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas

## Description

This pull request includes updates to the configuration files for
various linters and a minor update to the LICENSE file. The most
important changes include the addition of a new configuration file for
JSCPD, updates to the PowerShell PSScriptAnalyzer settings, and a
modification to the GitHub workflow for super-linter.

Linter configuration updates:

*
[`.github/linters/.jscpd.json`](diffhunk://#diff-557094e283c00b23265c1c75872f41c6b1a524a00f0d99dd68ebd22cb63bfdd6R1-R10):
Added a new configuration file for JSCPD to set the threshold to 0,
specify reporters, and ignore test files.
*
[`.github/linters/.powershell-psscriptanalyzer.psd1`](diffhunk://#diff-aae69c9d6774628ed181eacf53aee0f38eb6c2f53492cf3a5b7f7bdb6ef43b6aL1-L16):
Updated the PSScriptAnalyzer settings to enable specific rules and
configure their parameters, while also excluding certain rules.

GitHub workflow update:

*
[`.github/workflows/Linter.yml`](diffhunk://#diff-482e65806ed9e4a7320f14964764086b91fed4a28d12e4efde1776472e147e79R30):
Disabled JSON Prettier validation in the super-linter GitHub workflow.

Minor update:

*
[`LICENSE`](diffhunk://#diff-c693279643b8cd5d248172d9c22cb7cf4ed163a3c98c8a3f69c2717edd3eacb7L3-R3):
Updated the copyright year from 2024 to 2025.

## Type of change

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [ ] 📖 [Docs]
- [ ] 🪲 [Fix]
- [x] 🩹 [Patch]
- [ ] ⚠️ [Security fix]
- [ ] 🚀 [Feature]
- [ ] 🌟 [Breaking change]

## Checklist

<!-- Use the check-boxes [x] on the options that are relevant. -->

- [x] I have performed a self-review of my own code
- [x] I have commented my code, particularly in hard-to-understand areas