i18n: unify similar translation strings for edited items

[ramiy]

Some translation strings have the same meaning but different wording. This ticket unifies the language being used in error messages for ​items that could not be edited.

[ramiy]

The new format is: Sorry, this XXX could not be edited.

[SergeyBiryukov]

Thanks for the patch! Some notes:

• 'Sorry, X could not be edited' implies some kind of error: invalid ID, failed request, etc.
• 'Sorry, X cannot be edited' implies a more permanent state, which is the case for deprecated blogger_getTemplate() and blogger_setTemplate() methods, see [22914].

With that in mind, I'd suggest replacing those two strings with Sorry, this method is not supported.

The rest of the changes look good, though need some further adjustments for consistency.

[SergeyBiryukov]

In 46814:

XML-RPC: Unify some "could not be created/updated/deleted" error messages for consistency.

Props ramiy, SergeyBiryukov.
Fixes #48883.

[ramiy]

Replying to SergeyBiryukov:

Thanks for the patch! Some notes:

• 'Sorry, X could not be edited' implies some kind of error: invalid ID, failed request, etc.
• 'Sorry, X cannot be edited' implies a more permanent state, which is the case for deprecated blogger_getTemplate() and blogger_setTemplate() methods, see [22914].

With that in mind, I'd suggest replacing those two strings with Sorry, this method is not supported.

The rest of the changes look good, though need some further adjustments for consistency.

Even better! Thank you for the in depth review.