chore(deps): upgrade Escendit.Tools.Branding to v2.0.0

[snovak7]

Closes #289

Summary by Sourcery

Upgrade Escendit.Tools.Branding dependency to version 2.0.0 across the solution and refresh associated lock files.

Build:

• Update Escendit.Tools.Branding package version to 2.0.0 in central package management configuration.

Chores:

• Regenerate package lock files for affected projects to reflect updated dependency versions.

Summary by CodeRabbit

• Chores
  • Updated Escendit.Tools.Branding dependency to version 2.0.0 across all projects and lock files.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Upgrades the Escendit.Tools.Branding dependency to version 2.0.0 and refreshes related lock files across multiple projects to align with the new version.

File-Level Changes

Change	Details	Files
Bump Escendit.Tools.Branding package version and synchronize central package management configuration.	Update the Escendit.Tools.Branding package version in central package management configuration Ensure that all projects consuming this package reference the updated centrally-managed version	Directory.Packages.props
Regenerate NuGet lock files for projects using the updated dependency.	Update resolved dependency graph to reflect Escendit.Tools.Branding v2.0.0 Refresh transitive dependency versions and metadata as produced by the package restore process	src/Orleans/packages.lock.json src/ServiceDefaults/packages.lock.json src/Temporalio/packages.lock.json src/UserSecrets/packages.lock.json

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Files Reviewed (5 files)

• Directory.Packages.props - dependency version bump
• src/Orleans/packages.lock.json - lock file refresh
• src/ServiceDefaults/packages.lock.json - lock file refresh
• src/Temporalio/packages.lock.json - lock file refresh
• src/UserSecrets/packages.lock.json - lock file refresh

---

_{Reviewed by step-3.7-flash · 158,965 tokens}

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 3a10ab0f-ac80-4b5a-b2ce-d7b9cadb165e

📥 Commits

Reviewing files that changed from the base of the PR and between dea81f3 and 677c50f.

📒 Files selected for processing (5)

• Directory.Packages.props
• src/Orleans/packages.lock.json
• src/ServiceDefaults/packages.lock.json
• src/Temporalio/packages.lock.json
• src/UserSecrets/packages.lock.json

---

Walkthrough

This PR updates the Escendit.Tools.Branding NuGet package from version 1.2.0 to 2.0.0. The central package declaration in Directory.Packages.props is updated and reformatted, then the corresponding lock entries are synchronized across four project-specific packages.lock.json files.

Changes

Branding package v2 upgrade

Layer / File(s)	Summary
Central package version declaration Directory.Packages.props	Escendit.Tools.Branding version updated from 1.2.0 to 2.0.0 with self-closing tag formatting normalized across all package declarations.
Project lock file synchronization src/Orleans/packages.lock.json, src/ServiceDefaults/packages.lock.json, src/Temporalio/packages.lock.json, src/UserSecrets/packages.lock.json	Locked versions and contentHashes for Escendit.Tools.Branding updated to 2.0.0 across all four project targets under net10.0.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Poem

🐰 The branding is bumped, now shiny and new,
From one-point-two to the fabulous two!
Lock files aligned with a hop and a bound,
Escendit's tools updated all 'round.
thump thump 🌟

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The PR title clearly and concisely describes the main change: upgrading Escendit.Tools.Branding to v2.0.0, which is the primary objective of this changeset.
Linked Issues check	✅ Passed	The PR successfully addresses the requirement from issue #289 to bump Escendit.Tools.Branding to v2.0.0 across all relevant configuration files.
Out of Scope Changes check	✅ Passed	All changes in the PR are directly related to upgrading Escendit.Tools.Branding to v2.0.0; no out-of-scope modifications detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 289-update-branding

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}