chore: update devDependencies and peerDependencies

[vostrypet]

• Bump @semantic-release/changelog from 5.0.0 to 6.0.0
• Bump @semantic-release/git from 9.0.0 to 10.0.0
• Downgrade eslint-config-amex from 7.0.0 to 6.0.0
• Bump jest and jest-snapshot from 29.x to 30.x
• Bump semantic-release from 17.0.4 to 24.2.5
• Update peerDependency for jest to ^30.0.0

Description

Motivation and Context

How Has This Been Tested?

Types of Changes

• [ ] Bug fix (non-breaking change which fixes an issue)
• [ ] New feature (non-breaking change which adds functionality)
• [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
• [ ] Documentation (adding or updating documentation)
• [ ] Dependency update

Checklist:

• [ ] My change requires a change to the documentation and I have updated the documentation accordingly.
• [ ] My changes are in sync with the code style of this project.
• [ ] There aren't any other open Pull Requests for the same issue/update.
• [ ] These changes should be applied to a maintenance branch.
• [ ] I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Jest-Image-Snapshot?

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[vostrypet]

The goal of this pull request is to upgrade dependencies, specifically to enable upgrading to Jest 30 in the project. Currently, it's not possible to upgrade to Jest 30 due to the existing constraint "jest": ">=20 <=29" in the dependencies.

This is a breaking change because Jest 30 introduces changes to testing methods, which required modifications to the existing tests that were not compatible with version 20.x. The test updates were necessary to ensure compatibility with the new Jest version.

[project0]

any update on this?

[vielhuber]

any update on this?