[Snyk] Upgrade classnames from 2.3.2 to 2.5.1

[eronisking]

Snyk has created this PR to upgrade classnames from 2.3.2 to 2.5.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

---

• The recommended version is 4 versions ahead of your current version.

• The recommended version was released on 9 months ago.

Release notes

Package name: classnames

• 2.5.1 - 2023-12-29
  

  Prepare for release of version 2.5.1 (#351)

• 2.5.0 - 2023-12-28
  

  Prepare for release of version 2.5.0 (#344)

• 2.4.0 - 2023-12-26
  

  Prepare for release of version 2.4.0 (#338)

• 2.3.3 - 2023-12-25
  

  Prepare for release of version 2.3.3 (#308)

• 2.3.2 - 2022-09-13
  

  add missing registry for npm publish (#283)

from classnames GitHub release notes

---

Important

• Check the changes in this PR to ensure they won't cause issues with your project.
• This PR was automatically created by Snyk using the credentials of a real user.

---

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

• 🧐 View latest project report
• 📜 Customise PR templates
• 🛠 Adjust upgrade PR settings
• 🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Description by Korbit AI

What change is being made?

Upgrade the classnames package from version 2.3.2 to 2.5.1 in the cms-umbraco example's package.json.

Why are these changes being made?

This upgrade addresses potential security vulnerabilities and ensures compatibility with the latest features and bug fixes provided in the newer version of the classnames package. Keeping dependencies up-to-date is crucial for maintaining the security and stability of the project.

Is this description stale? Ask me to generate a new description by commenting /korbit-generate-pr-description

[korbit-ai]

👋 I'm here to help you review your pull request. When you're ready for me to perform a review, you can comment anywhere on this pull request with this command: /korbit-review.

As a reminder, here are some helpful tips on how we can collaborate together:

• To have me re-scan your pull request, simply re-invoke the /korbit-review command in a new comment.
• You can interact with me by tagging @korbit-ai in any conversation in your pull requests.
• On any comment I make on your code, please leave a 👍 if it is helpful and a 👎 if it is unhelpful. This will help me learn and improve as we work together
• Lastly, to learn more, check out our Docs.