Update dependency tzlocal to v4

[renovate[bot]]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
tzlocal	==2.1 -> ==4.2

---

Release Notes

regebro/tzlocal

### [`v4.2`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​42-2022-04-02) [Compare Source](https://togithub.com/regebro/tzlocal/compare/4.1...4.2) - If TZ environment variable is set to /etc/localhost, and that's a link to a zoneinfo file, then tzlocal will now find the timezone name, and not just return a localtime TZ object. ### [`v4.1`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​41-2021-10-29) [Compare Source](https://togithub.com/regebro/tzlocal/compare/4.0.2...4.1) - No changes from 4.1b1. ### [`v4.0.2`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​402-2021-10-26) [Compare Source](https://togithub.com/regebro/tzlocal/compare/4.0.1...4.0.2) - Improved the error message when you had a conflict including a /etc/localtime symlink. ### [`v4.0.1`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​401-2021-10-19) [Compare Source](https://togithub.com/regebro/tzlocal/compare/4.0...4.0.1) - A long time bug in Ubuntu docker images seem to not get fixed, so I added a workaround. ### [`v4.0`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​402-2021-10-26) [Compare Source](https://togithub.com/regebro/tzlocal/compare/3.0...4.0) - Improved the error message when you had a conflict including a /etc/localtime symlink. ### [`v3.0`](https://togithub.com/regebro/tzlocal/blob/HEAD/CHANGES.txt#​30-2021-08-13) [Compare Source](https://togithub.com/regebro/tzlocal/compare/2.1...3.0) - Modernized the packaging, moving to setup.cfg etc. - Handles if the text config files incorrectly is a TZ file. (revanSZ)

---

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Mend Renovate. View repository job log here.

[performance-testing-bot[bot]]

Unable to locate .performanceTestingBot config file

[viezly[bot]]

Pull request by bot. No need to analyze

[difflens[bot]]

View changes in DiffLens

[guide-bot[bot]]

Thanks for opening this Pull Request! We need you to:

1. Fill out the description.

   Action: Edit description and replace <!- ... --> with actual values.

2. Complete the activities.

   Action: Complete If you want to rebase/retry this PR, check this box

   If an activity is not applicable, use '\~activity description\~' to mark it not applicable.

[difflens[bot]]

View changes in DiffLens

[difflens[bot]]

View changes in DiffLens

[pull-request-quantifier-deprecated[bot]]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

``` Label : No Changes Size : +0 -0 Percentile : 0% Total files changed: 1 Change summary by file extension: .txt : +0 -0 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a balance between between PR complexity and PR review overhead. PRs within the optimal size (typical small, or medium sized PRs) mean: - Fast and predictable releases to production: - Optimal size changes are more likely to be reviewed faster with fewer iterations. - Similarity in low PR complexity drives similar review times. - Review quality is likely higher as complexity is lower: - Bugs are more likely to be detected. - Code inconsistencies are more likely to be detected. - Knowledge sharing is improved within the participants: - Small portions can be assimilated better. - Better engineering practices are exercised: - Solving big problems by dividing them in well contained, smaller problems. - Exercising separation of concerns within the code changes. #### What can I do to optimize my changes - Use the PullRequestQuantifier to quantify your PR accurately - Create a context profile for your repo using the [context generator](https://github.com/microsoft/PullRequestQuantifier/releases) - Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the `Excluded` section from your `prquantifier.yaml` context profile. - Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your `prquantifier.yaml` context profile. - Only use the labels that matter to you, [see context specification](./docs/prquantifier-yaml.md) to customize your `prquantifier.yaml` context profile. - Change your engineering behaviors - For PRs that fall outside of the desired spectrum, review the details and check if: - Your PR could be split in smaller, self-contained PRs instead - Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR). #### How to interpret the change counts in git diff output - One line was added: `+1 -0` - One line was deleted: `+0 -1` - One line was modified: `+1 -1` (git diff doesn't know about modified, it will interpret that line like one addition plus one deletion) - Change percentiles: Change characteristics (addition, deletion, modification) of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.