Make queue item expiration configurable via Java system property

[daniel-beck]

Related to https://issues.jenkins.io/browse/JENKINS-26228, https://issues.jenkins.io/browse/JENKINS-31039.

The cache we use doesn't seem to allow for a guaranteed minimum duration without allowing infinite growth, but tunable settings seem like a start (and in the future, increase defaults). I chose 10k as the max size to support busy instances without allowing them to go oom too easily, but this value is a wild guess. Even significant increases in duration seem to be the primary reason for cache eviction.

For now for the PR build and to allow feedback on approach.

---

See JENKINS-XXXXX.

Testing done

Ran java -Dhudson.model.Queue.LEFT_ITEMS_CACHE_EXPIRATION_SECONDS=20 -jar jenkins.war and confirmed items disappeared (/queue/item/NN/ 404) ~20 seconds after becoming LeftItems.

Proposed changelog entries

• human-readable text

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

@mention

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