Refine button appearances in sidebars, menus, pages and breadcrumbs

[janfaracik]

Small one to refine the appearance of buttons in sidebars, menus, pages and breadcrumbs. In a similar fashion to #9366 font sizes and spacing has been adjusted for consistency and to also align with whole pixels.

Before

After

Sidebars are now slightly more compact and less bold, allowing for more items on screen at once

Before

After

Buttons are slightly larger as a result of the increase in font size, bringing consistency with other font sizes

Before

After

Dropdowns are slightly less bold

Before

After

Breadcrumbs have had their font size adjusted slightly for consistency and to align with whole pixels

Testing done

• Using the Design Library everything looks as expected

Proposed changelog entries

• Refine button appearances in sidebars, menus, pages and breadcrumbs.

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

[timja]

LGTM

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

[0023-119]

So let's rephrase those changes: you basically made everything slightly bigger for no apparent reason, and yet you decided to remove the Disable job button in #9287 because it used few pixels of space?
This is ridiculous.