fix(debugging): emit probe status updates unconditionally

[P403n1x87]

We ensure that probe status update are sent when due, regardless of whether the RCM worker has found new data. This fixes a regression introduced by the IPC refactor for the RCM client.

Checklist

• Change(s) are motivated and described in the PR description.
• Testing strategy is described if automated tests are not included in the PR.
• Risk is outlined (performance impact, potential for breakage, maintainability, etc).
• Change is maintainable (easy to change, telemetry, documentation).
• Library release note guidelines are followed. If no release note is required, add label changelog/no-changelog.
• Documentation is included (in-code, generated user docs, public corp docs).
• Backport labels are set (if applicable)

Reviewer Checklist

• Title is accurate.
• No unnecessary changes are introduced.
• Description motivates each change.
• Avoids breaking API changes unless absolutely necessary.
• Testing strategy adequately addresses listed risk(s).
• Change is maintainable (easy to change, telemetry, documentation).
• Release note makes sense to a user of the library.
• Reviewer has explicitly acknowledged and discussed the performance implications of this PR as reported in the benchmarks PR comment.
• Backport labels are set in a manner that is consistent with the release branch maintenance policy

[shatzi]

nice fix

[github-actions]

The backport to 1.16 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.16 1.16
# Navigate to the new working tree
cd .worktrees/backport-1.16
# Create a new branch
git switch --create backport-6714-to-1.16
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1726105fe1825e52855aeabcae61233d22fa4692
# Push it to GitHub
git push --set-upstream origin backport-6714-to-1.16
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.16

Then, create a pull request where the base branch is 1.16 and the compare/head branch is backport-6714-to-1.16.

[github-actions]

The backport to 1.17 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.17 1.17
# Navigate to the new working tree
cd .worktrees/backport-1.17
# Create a new branch
git switch --create backport-6714-to-1.17
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1726105fe1825e52855aeabcae61233d22fa4692
# Push it to GitHub
git push --set-upstream origin backport-6714-to-1.17
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.17

Then, create a pull request where the base branch is 1.17 and the compare/head branch is backport-6714-to-1.17.

[github-actions]

The backport to 1.18 failed:

The process '/usr/bin/git' failed with exit code 1

To backport manually, run these commands in your terminal:

# Fetch latest updates from GitHub
git fetch
# Create a new working tree
git worktree add .worktrees/backport-1.18 1.18
# Navigate to the new working tree
cd .worktrees/backport-1.18
# Create a new branch
git switch --create backport-6714-to-1.18
# Cherry-pick the merged commit of this pull request and resolve the conflicts
git cherry-pick -x --mainline 1 1726105fe1825e52855aeabcae61233d22fa4692
# Push it to GitHub
git push --set-upstream origin backport-6714-to-1.18
# Go back to the original working tree
cd ../..
# Delete the working tree
git worktree remove .worktrees/backport-1.18

Then, create a pull request where the base branch is 1.18 and the compare/head branch is backport-6714-to-1.18.