release-25.2: jobs: update status tables with delete then insert

[blathers-crl]

Backport 1/1 commits from #147501 on behalf of @msbutler.

---

Previously, the auxillary job system tables were updated with an update stmt instead of a delete-then-insert approach to avoid an extra roundtrip to the kv layer. This optimization also included faulty error handling against a pk unique constraint violation. Specifically, these update paths would issue a delete if the internal executor returned an error on the update; however, the delete used the same txn as the original update, and the internal executor does not automatically clean up any uncommited data from the original update (i.e. via a savepoint rollback).

To avoid further complicating this optimization by wrapping the update in a savepoint, this commit simply reverts the update path to the original delete then insert pattern.

Epic: none

Release note: none

---

Release justification:

[blathers-crl]

Thanks for opening a backport.

Please check the backport criteria before merging:

• Backports should only be created for serious
  issues or test-only changes.
• Backports should not break backwards-compatibility.
• Backports should change as little code as possible.
• Backports should not change on-disk formats or node communication protocols.
• Backports should not add new functionality (except as defined
  here).
• Backports must not add, edit, or otherwise modify cluster versions; or add version gates.
• All backports must be reviewed by the owning areas TL. For more information as to how that review should be conducted, please consult the backport
  policy.

If your backport adds new functionality, please ensure that the following additional criteria are satisfied:

• There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
• The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
• New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters. State changes must be further protected such that nodes running old binaries will not be negatively impacted by the new state (with a mixed version test added).
• The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.
• Your backport must be accompanied by a post to the appropriate Slack
  channel (#db-backports-point-releases or #db-backports-XX-X-release) for awareness and discussion.

Also, please add a brief release justification to the body of your PR to justify this
backport.

[blathers-crl]

It looks like your PR touches production code but doesn't add or edit any test code. Did you consider adding tests to your PR?

_{🦉 Hoot! I am a Blathers, a bot for CockroachDB. My owner is dev-inf.}

[cockroach-teamcity]

This change is 

[jeffswenson]

LGTM