Coded values in Aurora popup URLs show label instead of coded value, inconsistent with web maps

Issue

Attribute values with a coded value domain that are pulled into a URL in a popup window (via {curly braces}) pull the label, not the coded value. This behavior is inconsistent with desktop web map/app where the coded value is pulled.

Example

For instance, suppose a hydrant point feature in a feature service has a field called, hydrant_type, and a coded value domain:

coded value	label
STK	Stack
PIL	Pillar
RND	Round

The popup has the following HTML code

This is a {hydrant_type} hydrant.
<a href="arcgis-survey123://?itemID=XXX&amp;field:HYDRANT_TYPE={hydrant_type}">Inspect this hydrant in Survey123</a>

In a web map, that popup for a pillar hydrant would look like this:

This is a Pillar hydrant.
<a href="arcgis-survey123://?itemID=XXX&amp;field:HYDRANT_TYPE=PIL">Inspect this hydrant in Survey123</a>

On Aurora, the popup looks like this:

This is a Pillar hydrant.
<a href="arcgis-survey123://?itemID=XXX&amp;field:HYDRANT_TYPE=Pillar">Inspect this hydrant in Survey123</a>

Note that the URL on Aurora shows the label rather than coded value.

It is important for passing data from Collector to Survey123 that the URL parameters pull the coded value so those codes can be matched to a Survey123 choice.

Per the Survey123 for ArcGIS topic on using that URL schema by @Cintruenigo:

The value to insert after the equal (=) sign is the actual value that will be stored in the feature service. If you are working with _selectone type of questions this is very relevant, since the value you must pass is that of the XLSForm Name of the choice, rather than its Label.