I'm seeing that sometimes we have a base62 ID & sometimes a GUID and takes work to see if they are the same. One option would be to add a mysql converstion function & then expose it as an api4 calculated field (slight gotcha - there is more than one field we might want to do it with)
ChatGPT was pretty forthcoming with a how-to(it would involve a stored procedure & a lookup table)
- or we could do via php - bearing in mind this would only affect the output display - using https://github.com/civicrm/civicrm-core/blob/6819eb05670f6b895d50aa30080985140197be04/Civi/Api4/Service/Spec/FieldSpec.php#L229