fix: avoid version changing for release type "none"

[AkatQuas]

Before, it would assemble unnecessary version change for packages, output example:

{
  changesets: [
    {
      releases: [Array],
      summary: 'composite',
      id: 'feat+image-new_2024-03-05'
    }
  ],
  releases: [
    {
      name: '@scopeA/image-filter',
      type: 'patch',
      oldVersion: '13.0.0',
      changesets: [Array],
      newVersion: '13.0.1'
    },
    {
      name: '@scopeB/app1',
      type: 'none',
      oldVersion: '1.0.0',
      changesets: [],
      newVersion: '1.0.0'
    },
    {
      name: '@scopeB/app2',
      type: 'none',
      oldVersion: '1.0.0',
      changesets: [],
      newVersion: '1.0.0'
    },
  ],
  preState: undefined
}

It would touch package.json in @scopeB/app1 and @scopeB/app2 with unnecessary IO event.

This Pull Request would skip such issue totally.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 9850d8e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[codesandbox-ci]

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

[AkatQuas]

Would you please review this at your convenience ? @Andarist . Thanks.