Extract added issues from the body of a revert commit

[axelniklasson]

Scan the body of revert commits for magic-word references — that's where manually added Fixes ENG-N notes live, not in the auto-generated Revert "..." subject. This fixes a bug in which the CLI ignored Fixes ENG-123 in a revert commit body, so the issue wasn't associated with the release.

Examples

A. Standard GitHub revert with a developer-added Fixes

Revert "Original feature" (#456)

Reverts org/repo#123

Fixes ENG-123

	issues	revertedIssues
Before	{}	{ENG-123}
After	{ENG-123}	{}

B. Same shape but with quoted content in the body

The case the greedy regex broke — the trailing " in the img tag closed the regex and swallowed the body.

Revert "Original feature" (#456)

Fixes ENG-123

<img alt="screenshot" src="https://example.com/x.png" />

	issues	revertedIssues
Before	{}	{ENG-123}
After	{ENG-123}	{}

C. Magic word in both the inner subject and the body — split correctly

Revert "Fixes ENG-100"

Fixes ENG-123

	issues	revertedIssues
Before	{}	{ENG-100}
After	{ENG-123}	{ENG-100}

[linear-code]

LIN-69678

[linear-code]

Left some comments. The fix correctly handles the message-body scan, but the early-return on odd branchDepth (line 201) short-circuits the whole function before afterTitle is ever considered — meaning the fix has no effect for the most common GitHub revert flow, where the branch IS named revert-<N>-<slug>.