Update job config title and breadcrumb depending on read only status

[janfaracik]

Updated the title and breadcrumb in configure.jelly for consistency:

• If the page is read only, they now display: 'Configuration'
• If the page isn't read only, they now display: 'Configure'

Also deleted the Save, Apply, and LOADING keys from Job configure resource bundles in all supported languages, as these are no longer used.

Before

After

Before

After

Testing done

• UI appears as expected

Proposed changelog entries

• N/A

Proposed changelog category

/label web-ui,skip-changelog

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.

Desired reviewers

@mention

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

Maintainer checklist

• 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).

[jtnord]

This seems incorrect to me.
The breadcrumb to me shows where you are - and you are viewing configuration.

That you may change the configuration by hitting save to me should not change the breadcrumb. Ie the action to get to a page is not the same as the breadcrumb for the page. They are likely to be related but actions would be nouns verbs and pages would be nouns

There is also SystemRead where you would never be performing an action on the actual page.

[daniel-beck]

"Configuration" works for when you're just viewing it (with Job/Extended Read), "Configure" does not.

[janfaracik]

Thanks - I've updated the PR:

• If the page is read only, they now display: 'Configuration'
• If the page isn't read only, they now display: 'Configure'