fix(registry): Fix a bug where recertify_registry is not called after a mutation

[jasonz-dfinity]

All registry mutations should be followed by recertify_registry. Otherwise the response from get_certified_changes_since call would be invalid as the RbTree is out-of-sync from the registry records.

Note that, as of Feb. 9th, 2026, no such proposals are executed or made. As long as this fix gets into the mainnet before any such proposals are made, there won't be any errors. In addition, even if such proposals are executed, we can recover simply by making ANY registry mutaions, including ones that can be called without proposals (e.g. update_node_operator_config_directly)

[github-actions]

This pull request changes code owned by the Governance team. Therefore, make sure that
you have considered the following (for Governance-owned code):

1. Update unreleased_changelog.md (if there are behavior changes, even if they are
   non-breaking).

2. Are there BREAKING changes?

3. Is a data migration needed?

4. Security review?

How to Satisfy This Automatic Review

1. Go to the bottom of the pull request page.

2. Look for where it says this bot is requesting changes.

3. Click the three dots to the right.

4. Select "Dismiss review".

5. In the text entry box, respond to each of the numbered items in the previous
   section, declare one of the following:

• Done.

• $REASON_WHY_NO_NEED. E.g. for unreleased_changelog.md, "No
  canister behavior changes.", or for item 2, "Existing APIs
  behave as before.".

Brief Guide to "Externally Visible" Changes

"Externally visible behavior change" is very often due to some NEW canister API.

Changes to EXISTING APIs are more likely to be "breaking".

If these changes are breaking, make sure that clients know how to migrate, how to
maintain their continuity of operations.

If your changes are behind a feature flag, then, do NOT add entrie(s) to
unreleased_changelog.md in this PR! But rather, add entrie(s) later, in the PR
that enables these changes in production.

Reference(s)

For a more comprehensive checklist, see here.

GOVERNANCE_CHECKLIST_REMINDER_DEDUP

[yhabib]

LGTM

[pierugo-dfinity]

Nice!

Trivial change