net/udpbroadcastrelay readability on other than default themes

[erdnuesse]

Important notices Before you add a new report, we ask you kindly to acknowledge the following:

• [X] I have read the contributing guide lines at https://github.com/opnsense/plugins/blob/master/CONTRIBUTING.md
• [X] I have searched the existing issues, open and closed, and I'm convinced that mine is new.
• [X] The title contains the plugin to which this issue belongs

On different themes you can't read any rule that's marked as active. (screenshot) That's because the css marks the whole line in bright colors.

Yes, I thought about upstreaming the issue to the theme devs, but: Other Plugins follow different rules of highlighting the lines (ie. wireguard) so my take is, the plugin says how it wants its lines formatted, and othe plugins use the default and IMHO correct design principles. On dark themes this one is pretty much unusable.

And switching themes to use one plugin is just urrrrrr

Steps to reproduce the behavior:

1. Use a dark theme that colors the whole area dark, not just header and menu items.
2. Go to udp broadcast relay
3. have at least one active rule
4. See the line in bright letters on bright bg
5. https://your_opnsense/ui/udpbroadcastrelay

Expected behavior more like wireguard

(that being said, firewall rules have another design language altogether, so I'd like to see them with ticks (like wg) rather than yellow/green which is SUPER user-unfriendly, maybe especially (my guess?) for colorblind people. But I even struggle sometimes with them.)

Screenshots

Relevant log files

Additional context the design language on which fields are shown to select and status of entries should be way more strict and concise to
a) avoid this type of rogue behavior when it comes to themes but almost more importantly to b) unify the workflow and ease the user to be able to trust on the same design principles across functionality of the whole opnsense stack (ticked means active, change of color should only be managed by themes, multi-select should always be a separate column, etc.)

so whoever knows where to flag this as unifying the UX design to be more consistent, feel free to additionally relay this aside from the initial issue of readability, but the latter is truly a hindrance.

Environment all the latest ones

OPNsense 24.7.5-amd64 AMD GX-412TC SOC