Display how many users there are on the 'Users' page

[janfaracik]

Tiny one to show how many users there are on the 'Users' page. Follows the same pattern as the prototype.

Testing done

• Shows how many users there are
• Displays 0 when there are no users

Proposed changelog entries

• Display how many users there are on the 'Users' page

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]

Don't we use badges in other areas for the same thing? When should I use a badge and when this new style? It makes sense to clarify in the design library?

[janfaracik]

Don't we use badges in other areas for the same thing? When should I use a badge and when this new style? It makes sense to clarify in the design library?

Opened a PR for the design library here - jenkinsci/design-library-plugin#325.

Gist is show a badge in the side panel for important info/info the user might need to take action on (e.g. updates, test success/failures) and show that in the app bar if that makes sense too. In this instance the number of users isn't important unless you're on this page, so there isn't value in showing it outside of this page as a badge.

[timja]

LGTM, could maybe format the number but may not affect many places:

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