🌟 [Feature]: Rename AutoCleanup to CleanupPrereleases and separate cleanup from release type

[MariusStorhaug]

The prerelease cleanup setting is now clearer and more intuitive. The AutoCleanup setting has been renamed to CleanupPrereleases, and the cleanup decision is now independent from the release type. This means you can control cleanup behavior separately from whether you're creating a release, prerelease, or no release at all.

• Related to 🩹 [Patch]: When a PR is closed, but not merged, fast forward to cleanup of prereleases. Process-PSModule#73
• Part of [Feature]: Add ReleaseType input to Publish-PSModule for explicit release control Process-PSModule#265

Renamed setting from AutoCleanup to CleanupPrereleases

The Publish.Module.AutoCleanup setting has been renamed to Publish.Module.CleanupPrereleases for clarity. The setting still defaults to true.

Before:

Publish:
  Module:
    AutoCleanup: true

After:

Publish:
  Module:
    CleanupPrereleases: true

Cleanup is now independent from ReleaseType

Previously, ReleaseType could be set to Cleanup to trigger prerelease cleanup. Now, ReleaseType only has three values: Release, Prerelease, or None. The cleanup decision is computed separately based on:

1. Whether you're in a cleanup scenario (merging to main or abandoning a PR)
2. Whether CleanupPrereleases is enabled in your settings (defaults to true)

The computed Run.CleanupPrereleases value is passed to the workflow and will be true when both conditions are met.

New Run.CleanupPrereleases output

A new Run.CleanupPrereleases property is now included in the settings output. This computed value tells the workflow whether prereleases should be cleaned up based on the current context and user settings.