Finish French translations for Update Center

[Mysterious-Dev]

All is in the title ^^.

Proposed upgrade guidelines

N/A

Submitter checklist

Beta Give feedback

1. The Jira issue, if it exists, is well-described.
2. 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.
3. There is automated testing or an explanation as to why this change has no tests.
4. New public classes, fields, and methods are annotated with @Restricted or have @since TODO Javadocs, as appropriate.
5. New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
6. 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).
7. For dependency updates, there are links to external changelogs and, if possible, full differentials.
8. 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

Beta Give feedback

1. There are at least two (2) approvals for the pull request and no outstanding requests for change.
2. Conversations in the pull request are over, or it is explicit that a reviewer is not blocking the change.
3. Changelog entries in the pull request title and/or Proposed changelog entries are accurate, human-readable, and in the imperative mood.
4. Proper changelog labels are set so that the changelog can be generated automatically.
5. 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).
6. 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).

[MarkEWaite]

They seem reasonable to me. I checked translate.google.com to convert them back to my native language (English) and the resulting English translation is good.

Would like one of the native French speakers to review and approve as well. @dduportal or @smerle33 or @lemeurherve or @gounthar

[Mysterious-Dev]

@gounthar I changed ^^.

[gounthar]

Looks good to me, thanks.

[hervelemeur]

Small suggestion, LGTM otherwise.

[hervelemeur]

Suggested change

	Your\ browser\ will\ reload\ automatically\ when\ Jenkins\ is\ ready.=Votre navigateur se connectera automatiquement quand Jenkins sera prêt.
	Your\ browser\ will\ reload\ automatically\ when\ Jenkins\ is\ ready.=Votre navigateur se rafraîchira automatiquement quand Jenkins sera prêt.

[Mysterious-Dev]

Small suggestion, LGTM otherwise.

@hervelemeur I applied your suggestion ^^.

[lemeurherve]

Thanks!

[MarkEWaite]

/label ready-to-merge

This PR is now ready for merge. We will merge it after approximately 24 hours if there is no negative feedback.

[comment-ops-bot]

I wasn't able to add the following labels: ready-to-merge

Check that the label exists and is spelt right then try again.

[MarkEWaite]

I've labeled it as skip-changelog because the submitter did not retain the pull request template and did not provide a proposed changelog entry. @Mysterious-Dev if you would like it mentioned in the changelog, could you update the pull request to use the template and include a proposed changelog entry? No issue for me if we don't mention it in the changelog as well.

Thanks again for the contribution!

[Mysterious-Dev]

I've labeled it as skip-changelog because the submitter did not retain the pull request template and did not provide a proposed changelog entry. @Mysterious-Dev if you would like it mentioned in the changelog, could you update the pull request to use the template and include a proposed changelog entry? No issue for me if we don't mention it in the changelog as well.

Thanks again for the contribution!

No that's fine. You can keep this excluded from the changelog ^^.