Describe a specific, valid use case where `git cherry-pick` is the most efficient way to apply a bug fix from one development line to another active release line without full branch merges.

A specific, valid use case where `git cherry-pick` is the most efficient way to apply a bug fix from one development line to another active release line without full branch merges is when a critical bug is discovered in a production release, and the fix is developed and committed on an active feature or development branch (`develop`), but needs to be immediately applied to a stable release branch (`release-1.0`) without introducing any other unrelated changes from the development branch. Here’s a detailed breakdown of the scenario and why `git cherry-pick` is optimal: Scenario: Imagine a software project that maintains two long-lived branches: `develop` and `release-1.0`. The `develop` branch serves as the primary development line, where new features are actively built, integrated, and undergo continuous evolution. The `release-1.0` branch is the release line, a stable branch from which version 1.0 of the software was released to customers. This release line is actively maintained for critical bug fixes that may lead to subsequent patch releases (e.g., 1.0.1, 1.0.2). A critical bug is reported in the 1.0 production release. A developer investigates and implements a fix. This fix is part of ongoing development and is committed to the `develop` branch as a single, self-contained commit (a snapshot of the repository at a specific point in time, along with metadata like author, date, and message). The `develop` b....