build(deps): Bump taskcluster from 24.0.1 to 24.1.0 in /tools

[dependabot-preview]

Bumps taskcluster from 24.0.1 to 24.1.0.

Release notes

Sourced from taskcluster's releases.

v24.1.0

▶ [minor] bug 1599122
Worker Manager now does a better job at keeping provisioning in-sync with reality.

• Workers now have a top-level capacity field which is how many tasks it can run at once.
• Workers now have lastModified and lastChecked fields which are useful for determining
  the state the worker is actually in vs what state Taskcluster thinks it is in.
• When calling createWorker manually, you can now specify a capacity for the worker.

▶ [minor] bug 1587511
WorkerPools can now be configured to terminate workers that fail to register after some amount of time.
Both of the google and aws providers now support a lifecycle object that for now has a single key
of registrationTimeout. It is optional and if it is provided the value is an integer with the number
of seconds a worker has to register before it is terminated.

This helps catch misconfigured or broken workers before they become zombies or worse.

▶ [patch] #217
Taskcluster UI no longer displays duplicated app bars when connecting via SSH.

▶ [patch] bug 1595749
Taskcluster login now properly handles an edge case where a couple of users were hitting which prevented them to login.

▶ [patch] bug 1599550
The auth.sentry_* Helm parameters are no longer required. If they are omitted, then the service will start up but the auth.sentryDSN REST API method will return 404's.

▶ [patch] bug 1599893
Worker Manager now takes optional configuration to change the timings on the lib-iterate loops
that control provisioning. The values are worker_manager.provisioner_iterate_config and
worker_manager.worker_scanner_iterate_config. Each is a JSON object where you can set the following:

• maxFailures - Which sets how many iterations in a row can fail before the task crashes
• maxIterationTime - How long (in ms) an iteration is allowed to take before it is ended
• waitTime - How long (in ms) to wait in between loops

▶ Additional changes not described here: #2114, #2130, bug 1577839.

v24.0.2

▶ [patch] bug 1602642
The typo in configuration for aws s3 bucket credentialing is fixed.

It was set as allowdBuckets and is now allowedBuckets

Changelog

Sourced from taskcluster's changelog.

v24.1.0

▶ [minor] bug 1599122
Worker Manager now does a better job at keeping provisioning in-sync with reality.

• Workers now have a top-level capacity field which is how many tasks it can run at once.
• Workers now have lastModified and lastChecked fields which are useful for determining
  the state the worker is actually in vs what state Taskcluster thinks it is in.
• When calling createWorker manually, you can now specify a capacity for the worker.

▶ [minor] bug 1587511
WorkerPools can now be configured to terminate workers that fail to register after some amount of time.
Both of the google and aws providers now support a lifecycle object that for now has a single key
of registrationTimeout. It is optional and if it is provided the value is an integer with the number
of seconds a worker has to register before it is terminated.

This helps catch misconfigured or broken workers before they become zombies or worse.

▶ [patch] #217
Taskcluster UI no longer displays duplicated app bars when connecting via SSH.

▶ [patch] bug 1595749
Taskcluster login now properly handles an edge case where a couple of users were hitting which prevented them to login.

▶ [patch] bug 1599550
The auth.sentry_* Helm parameters are no longer required. If they are omitted, then the service will start up but the auth.sentryDSN REST API method will return 404's.

▶ [patch] bug 1599893
Worker Manager now takes optional configuration to change the timings on the lib-iterate loops
that control provisioning. The values are worker_manager.provisioner_iterate_config and
worker_manager.worker_scanner_iterate_config. Each is a JSON object where you can set the following:

• maxFailures - Which sets how many iterations in a row can fail before the task crashes
• maxIterationTime - How long (in ms) an iteration is allowed to take before it is ended
• waitTime - How long (in ms) to wait in between loops

▶ Additional changes not described here: #2114, #2130, bug 1577839.

v24.0.2

▶ [patch] bug 1602642
The typo in configuration for aws s3 bucket credentialing is fixed.

It was set as allowdBuckets and is now allowedBuckets

Commits

• b2b523d v24.1.0
• 0a81977 Merge pull request #2153 from helfi92/speed-dial-nit
• 33bad3e Add silent changelog
• ab3c74a Add escapeKeyDown on SpeedDial
• 20d15d3 Merge pull request #2121 from helfi92/remove-nav-bar-interactive-session
• 2b187d6 Add marginRight to list item left icon
• 9990ee8 remove changelog entry that was in 24.0.2
• f9b95f2 Merge branch 'v24.0.x'
• e3c4269 v24.0.2
• b81db50 Merge pull request #2150 from taskcluster/allowdBuckets
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)