Fix a few Finnish translations

[KalleOlaviNiemitalo]

Fix some Finnish translations. This doesn't add any new translations, and mostly doesn't remove obsolete ones either.

Testing done

Not yet. I intend to test during the week starting on 2025-07-07.

Proposed changelog entries

• correct a few Finnish translations

Proposed changelog category

/label localization

Proposed upgrade guidelines

N/A

Submitter checklist

• The Jira issue, if it exists, is well-described.
  • No Jira issue. I'm not proposing this for LTS backport.
• 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.
  • No changes in Java code.
• New deprecations are annotated with @Deprecated(since = "TODO") or @Deprecated(forRemoval = true, since = "TODO"), if applicable.
  • No changes in Java code.
• 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).
  • No changes in JavaScript code.
• For dependency updates, there are links to external changelogs and, if possible, full differentials.
  • No changes in dependencies.
• For new APIs and extension points, there is a link to at least one consumer.
  • No API changes.

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

[welcome]

Yay, your first pull request towards Jenkins core was created successfully! Thank you so much!

A contributor will provide feedback soon. Meanwhile, you can join the chats and community forums to connect with other Jenkins users, developers, and maintainers.

[KalleOlaviNiemitalo]

https://www.jenkins.io/doc/developer/crowdin/translating-plugins/ refers to https://crowdin.jenkins.io/, but I don't see the Jenkins core in the list of open projects.

I am a native speaker of Finnish but not a professional translator.

I can squash all commits together if preferred.

[MarkEWaite]

https://www.jenkins.io/doc/developer/crowdin/translating-plugins/ refers to https://crowdin.jenkins.io/, but I don't see the Jenkins core in the list of open projects.

You are correct that we are not yet using CrowdIn for Jenkins core. It is only enabled for plugins at the moment. More work is needed before it would ready for use on Jenkins core.