Fix Schema System Check translation and show missing Custom Field ID

[mlutfy]

Overview

When the Schema System Check finds a smartgroup using deleted Custom Fields, it just says that the field is deleted. This is not terribly useful, either to fix the saved search, or to do a bit of archaeology using logging tables.

Also, this PR fixes the translation of strings.

Before

After

[civibot]

(Standard links)

• If this is your first pull-request for CiviCRM, please browse CONTRIBUTING.md for information about the development and testing processes.
• If you are reviewing this pull-request, you may wish to consult the test sites and the Review Standards (long template, short template).

[demeritcowboy]

This was also there before but I'm not clear on what "errors on group page" means. Maybe it should be "This may cause errors when using the group." Or even just "This may cause errors.". At the very least it should have a "the" in it, but I don't know what "the group page" is referring to.

[mlutfy]

I updated for now to "This may cause errors when recalculating the smart group counts", because I think that's the most
accurate problem, and it's also the name of the button on the "Manage Groups" page (I'd refer to the name of that section explicitly, but I couldn't find a non-awkward way to say it).

but will circle back

[mlutfy]

@demeritcowboy Thanks for the review! I updated the string again to this:

The following smart groups include custom fields which are disabled or deleted from the database. Missing fields should automatically be ignored from the smart group criteria, but you may want to review and update their search criteria to remove the outdated fields.

I think it's more accurate this way, because as far as I know, smart groups do not crash when a field is removed, and people should not be too worried about it (but it can be very useful to catch an error such as, removing a field, which ends up altering the meaning of smart-groups).

[demeritcowboy]

I don't want to bog this down too much since this PR wasn't about the wording, but what happens is that the group ends up including way more people. E.g. if you have a smart group that filters on contact type = Student and custom field A = "something", then you disable/delete the custom field, the group now includes ALL students whenever it gets used.

So how about let's merge this to get the field ID and ts fixes, and can think about the wording.

[demeritcowboy]

One of the extra question marks was still there so have put up #23480