[JENKINS-69904] _safeRestart.jelly must not use parentheses in localizable messages

[dwnusbaum]

See JENKINS-69904 and #7091.

This PR also deletes all existing translations since #7091 made them obsolete.

Testing done

Here's a screenshot of the /safeRestart page with these changes

I could add a WebClient test that just navigates to this page if desired, but I'm not sure how valuable that would be. Let me know if you want to me to add this.

Proposed changelog entries

• Prevent exception from being thrown when attempting to initiate a safe restart (regression in 2.374)

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
• The changelog entries and upgrade guidelines are appropriate for the audience affected by the change (users or developers, depending on the change) and are in the imperative mood (see examples).
  • Fill in the Proposed upgrade guidelines section only if there are breaking changes or changes that may require extra steps from users during upgrade.
• There is automated testing or an explanation as to why this change has no tests.
• New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
• New or substantially changed JavaScript is not defined inline and does not call eval to ease future introduction of Content Security Policy (CSP) directives (see documentation).
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
• For new APIs and extension points, there is a link to at least one consumer.

Maintainer checklist

Before the changes are marked as ready-for-merge:

• There are at least two (2) approvals for the pull request and no outstanding requests for change.
• Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
• Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
• Proper changelog labels are set so that the changelog can be generated automatically.
• If the change needs additional upgrade steps from users, the upgrade-guide-needed label is set and there is a Proposed upgrade guidelines section in the pull request title (see example).
• If it would make sense to backport the change to LTS, a Jira issue must exist, be a Bug or Improvement, and be labeled as lts-candidate to be considered (see query).

[timja]

we should alter existing translation files so that the existing translations continue to be used even though they no longer reflect the current version of the English text. Let me know if you want me to make any changes.

Generally we remove all translations that no longer match the English text so that they get retranslated.

[dwnusbaum]

Generally we remove all translations that no longer match the English text so that they get retranslated.

Ok, I think I deleted them all in e4631cc.

[timja]

/label ready-for-merge

---

This PR is now ready for merge, after ~24 hours, we will merge it if there's no negative feedback.

Thanks!

[Wadeck]

Thanks Devin 👍