Minor footer appearance tweaks

[janfaracik]

Minor footer tweaks to bring it more inline with the ongoing design work.

• The links now uses the .jenkins-button classes, giving them better focus states and larger hitboxes
• The version number is clickable, offering helpful links to About Jenkins, Get involved, and the Jenkins website
• The footer hides on mobile now

Testing done

• Footer works as before
• Version dropdown works

Proposed changelog entries

• Minor footer appearance tweaks

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

@jenkinsci/sig-ux

Maintainer checklist

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

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

[timja]

cc @imonteroperez @Vlatombe in case this impacts your product.

[NotMyFault]

That should probably be hidden, in case the user lacks Overall/Administer or Overall/SystemRead.

[timja]

actually manage or system read

[NotMyFault]

That's what ci.j reported 👀

[janfaracik]

Updated, let me know if that's the right permission 👍

[NotMyFault]

The simple-theme plugin might need an update too.

[timja]

The simple-theme plugin might need an update too.

The simple theme plugin doesn't do that as far as I know. it will be a third party theme that is not maintained from what I can see. I wouldn't worry about it.

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