Add line-level, blame-based suspect commits for Azure DevOps

Problem Statement For projects using Azure DevOps Git repositories, Sentry can identify suspect commits from release commit data, but that can point to a commit that merely changed the same file—not the one that changed the line involved in the error. For example, a large merge commit can be suggested instead of a later, focused fix. This makes the widget misleading and harder to trust. Solution Brainstorm When an Azure DevOps repository is connected and code mappings are configured, use the relevant stack frame’s file and line to identify the commit that introduced or last changed that line. This could use Azure Repos blame data or an equivalent file-history approach. Keep release-based matching as a fallback when line-level attribution isn’t available. Expected behavior • Use mapped source paths and line numbers from the error stack trace. • Prefer the commit associated with the relevant line over other commits that changed the same file in the release. • Handl…