Inconsistent behavior between server and iadmin if zone name contains special chars

[ll4strw]

OS: Ubuntu 22.04.3 LTS
iRODS: v4.3.1

This issue was first mentioned in irods/irods_api_plugin_genquery2#97 (comment)

While the iRODS server does not allow at start time to have a zone which name contains special chars

irods.exceptions.IrodsError: ERROR: Validation Failed for [/etc/irods/server_config.json]:
	against [file:///var/lib/irods/configuration_schemas/v4/server_config.json]
	ValidationError: 'überZone' does not match '^[A-Za-z0-9_\\.]+$'

Failed validating 'pattern' in schema['properties']['zone_name']:
    {'maxLength': 63, 'pattern': '^[A-Za-z0-9_\\.]+$', 'type': 'string'}

On instance['zone_name']:
    'überZone'

iadmin does. For instance,

#!/bin/env bash
zone=$(printf '\xc3\xbcberZone')
iadmin modzone testZone name $zone

succeeds and iRODS works as expected. Would it be possible to have a consistent behavior in the treatment of special chars, please?
This would make sure that an admin that modified a zone name to contain special chars will still be able to restart the server in case of need.