Enhancement: Explain behavior of unset app config boolean to user

[shamoon]

Proposed change

Small QoL UX thing I'd like to sneak into 2.3.3 that I forgot to resolve with app config. Basically the form currently shows boolean fields as having a value (e.g. disabled) but they're actually null until the user actually toggles it on or off meaning they dont yet apply. This just adds a little visual warning as such. Screenshots below hopefully show what I mean.

Closes #5126 (comment)

Type of change

• Bug fix: non-breaking change which fixes an issue.
• New feature: non-breaking change which adds functionality. Please read the important note above.
• Breaking change: fix or feature that would cause existing functionality to not work as expected.
• Documentation only.
• Other. Please explain: Change / enhancement / kind of fix

Checklist:

• I have read & agree with the contributing guidelines.
• If applicable, I have included testing coverage for new code in this PR, for backend and / or front-end changes.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.
• If applicable, I have checked that all tests pass, see documentation.
• I have run all pre-commit hooks, see documentation.
• I have made corresponding changes to the documentation as needed.
• I have checked my modifications for any breaking changes.

[stumpylog]

Makes sense to me, hopefully will reduce confusion

[cdoepmann]

Perfect, thanks a lot for resolving this so quickly before I could even open a proper discussion or issue!

[github-actions]

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion or issue for related concerns.