[Feature] Custom field UI excessive character handling

[sleetx]

Custom fields that exceed a character limit should be automatically collapsed or truncated in the UI. And only fully visible when deliberately revealed by the user. A common way to do this is with clickable ellipsis “…”

Some plugins are being designed to hold very large data sets in individual custom fields that disrupt the performer page UI, pushing the performer's other fields and list of scenes very far down the page.

Relevant discord discussion: https://discord.com/channels/559159668438728723/742220889017417738/1384552641656520846

Example:

[cj12312021]

I would argue the onus is on the plugin developer to ensure that fields they did not intend to be rendered are not rendered. This PR that I submitted a few weeks ago patches the CustomFields component to prevent the base64-encoded image provided by my plugin as a custom field from being rendered. Other plugin developers can also leverage that work.

Users viewing details in the expanded view will expect all details to be expanded, even custom field details.

[feederbox826]

I think the best way to handle this would be by assigning the field name as an id to the element, this would allow handling to be done completely in CSS and give full flexibility to hide, limit, show, scale etc or even modify with JS