Migrate JobLog page to API4

[braders]

Overview

Migrate JobLog page to API4

Before

The JobLog page was written in the traditional CiviCRM way using the DAO object. This led to notices on the JobLog screen from undefined array keys:

Given that up to 1000 rows are shown at the time this could lead to significant noise in the site logs.

After

The JobLog page now uses API4. API4 keys are always set (unlike DAO objects which didn't set properties for NULL values), meaning that no undefined array key warnings occur.

To faciltate this JobLog entitites are now exposed over the API.

I have also done some minor tidy-up of the JobLog template:

• The $sj variable was being set, but not referenced. Now removed.
• jobName and jobRunUrl are now always set, reducing reliance on empty in the Smarty template (which I think is preferable when in CIVICRM_SMARTY_DEFAULT_ESCAPE mode).

Comments

I'm never quite sure how quickly PRs make it into a release, so the @since 5.56 is a bit of a guess on the new API entity.

I settled on @searchable secondary, but I think it's borderline whether this should be secondary or none. I don't really mind either way.

See also dev/core#2486

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[eileenmcnaughton]

I gave this an r-run & it worked. I also dug into the permissions a little bit & will put up a follow up that tweaks core permissions & switches to checkPermissions false

[eileenmcnaughton]

I put up this follow up #24619