Pull Request for Issue #38737.

Summary of Changes

This PR checks if the field type being shown in the user profile is a subform.

If the field is a subform and has a fieldname set to "row", the profile thinks there is no custom field with that name. So, we must set the fieldname back to the original name of the custom field by pulling it from $field->name. (Confused yet?) Now the layout correctly finds and displays the custom field value.

See comments in issue as to why I am doing it this way instead of fixing the problem at the root. This is the only place in core where we are looking for custom field values by the fieldname instead of passing it through the field plugin to render it.

Testing Instructions

Create a user field of type text with "Onle Us In Subform"
Create a user subform field with the textfield
Create a menu item of type "user profile"
Login in frontend, edit your user and fill the subform field with at least one row.
Save your profile.

Actual result BEFORE applying this Pull Request

In the profile view the subform field value is missing.

Expected result AFTER applying this Pull Request

In the profile view the subform field shows as expected.

Documentation Changes Required

None.