fix(ng-dev/commit-message): harden git log commit parsing against delimiter and metadata smuggling

[josephperrott]

Summary

• ng-dev/release: Replace the printable delimiter (-------------ɵɵ------------) in fetchCommitsForRevisionRange with a NUL byte (%x00 / \0) so commit bodies containing printable text cannot forge commit boundaries during release notes generation.
• ng-dev/commit-message & ng-dev/release: Extract the trailing -hash-, -shortHash-, and -author- fields from git log output before passing the commit body to conventional-commits-parser (with fieldPattern disabled), preventing commit body content or git scissor lines (# ------------------------ >8 ------------------------) from spoofing or truncating commit metadata. Additionally sanitize hash and shortHash in RenderContext.commitToLink and RenderContext.commitToBadge to strip Markdown link control characters.

[gemini-code-assist]

Code Review

This pull request improves the robustness and security of commit message parsing and release notes generation. It introduces regex-based extraction of git log metadata to prevent body metadata smuggling, replaces the commit split delimiter with a null byte to avoid accidental splitting, and sanitizes commit hashes to prevent Markdown injection. Feedback on the changes highlights a bug in parseInternal where an empty commit message with metadata would incorrectly fall back to parsing the raw metadata; passing messageText directly to the parser is suggested to resolve this.