Update the appearance of the stop button

[janfaracik]

Small MR to update the appearance of the stop button component.

Before

After

Testing done

• Component works as before, doesn't cause layout shifts

Proposed changelog entries

• Update the appearance of the stop button.

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

@jenkinsci/sig-ux

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

[uhafner]

UI looks good, Thanks!

One localization is broken now.

[uhafner]

This will break the i18n, it would be better to use Cancel in the properties as {en} translation. Or rename all translations.

[timja]

Tests failing

[yaroslavafenkin]

Looks OK security wise.

---

Is it just me or alignment is off? Nor aligned with the progress bar, neither with #1.

[daniel-beck]

alignment is off

Not newly introduced per screenshots in PR comment.

[timja]

alignment is off

Not newly introduced per screenshots in PR comment.

similar-ish things noticed here:
#8761 (review)

a few things looking a bit funny but they were already in that state.

[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!

[DuMaM]

Thanks :D I was waiting so long for this change.