deps(go): bump module github.com/Masterminds/semver/v3 to v3.5.0

[updateclibot]

deps(go): bump module github.com/Masterminds/semver/v3

clean: go mod tidy

ran shell command "go mod tidy"

deps(go): bump module github.com/Masterminds/semver/v3 to v3.5.0

go.mod updated Module path "github.com/Masterminds/semver/v3" version from "v3.4.0" to "v3.5.0"

v3.5.0

## What's Changed
* Adding more prerelease tests by @mattfarina in https://github.com/Masterminds/semver/pull/273
* Update constraint error messages by @mattfarina in https://github.com/Masterminds/semver/pull/278
* Fix edge cases by @mattfarina in https://github.com/Masterminds/semver/pull/279
* Adding some checks in by @mattfarina in https://github.com/Masterminds/semver/pull/280
* Updating deps by @mattfarina in https://github.com/Masterminds/semver/pull/281
* Bump github/codeql-action from 4.35.1 to 4.35.2 by @dependabot[bot] in https://github.com/Masterminds/semver/pull/282
* Bump actions/cache from 4.2.3 to 5.0.5 by @dependabot[bot] in https://github.com/Masterminds/semver/pull/283
* Bump golangci/golangci-lint-action from 7.0.1 to 9.2.0 by @dependabot[bot] in https://github.com/Masterminds/semver/pull/284
* Updating gitignore for devcontainers by @mattfarina in https://github.com/Masterminds/semver/pull/286
* Fixing some quality issues by @mattfarina in https://github.com/Masterminds/semver/pull/287

## New Contributors
* @dependabot[bot] made their first contribution in https://github.com/Masterminds/semver/pull/282

**Full Changelog**: https://github.com/Masterminds/semver/compare/v3.4.0...v3.5.0

v3.4.0

There are a few changes in this release to highlight:

1. `Constraints` now has a property `IncludePrerelease`. When set to true the `Check` and `Validate` methods will include prereleases.
2. When an AND group has one constraint with a prerelease but more than one constraint then prereleases will be included. For example, `>1.0.0-beta.1 < 2`. In the past this would not have included prereleases because each constraint needed to have a prerelease. Now, only one constraint needs to have a prerelease. This is considered a long standing bug fix. Note, this does not carry across OR groups. For example, `>1.0.0-beta.1 < 2 || > 3`. In this case, prereleases will not be included when evaluating against `>3`.
3. `NewVersion` coercion with leading "0"'s is restored. This can be disabled by setting the package level property `CoerceNewVersion` to `false`.


## What's Changed
* fix the CodeQL link by @dmitris in https://github.com/Masterminds/semver/pull/257
* Restore detailed errors when failed to parse with NewVersion by @mattfarina in https://github.com/Masterminds/semver/pull/262
* updating go version tested with by @mattfarina in https://github.com/Masterminds/semver/pull/263
* Restore the ability to have leading 0's with NewVersion by @mattfarina in https://github.com/Masterminds/semver/pull/266
* Handle pre-releases on all in an and group by @mattfarina in https://github.com/Masterminds/semver/pull/267
* Add property to include prereleases by @mattfarina in https://github.com/Masterminds/semver/pull/268
* Updating the error message handling by @mattfarina in https://github.com/Masterminds/semver/pull/269
* Update the release notes and readme for new version by @mattfarina in https://github.com/Masterminds/semver/pull/270

## New Contributors
* @dmitris made their first contribution in https://github.com/Masterminds/semver/pull/257

**Full Changelog**: https://github.com/Masterminds/semver/compare/v3.3.1...v3.4.0

GitHub Action workflow link

---

Created automatically by Updatecli Options: Most of Updatecli configuration is done via its manifest(s). If you close this pull request, Updatecli will automatically reopen it, the next time it runs. If you close this pull request and delete the base branch, Updatecli will automatically recreate it, erasing all previous commits made. Feel free to report any issues at github.com/updatecli/updatecli. If you find this tool useful, do not hesitate to star our GitHub repository as a sign of appreciation, and/or to tell us directly on our chat!