Bump SharpZipLib from 1.2.0 to 1.3.3 in /tools/Updater/Updater

[dependabot]

Bumps SharpZipLib from 1.2.0 to 1.3.3.

Release notes

Sourced from SharpZipLib's releases.

v1.3.3

Another minor release, containing security fixes and smaller bugfixes.

Fixes:

• 🐛 specialized tar extract traversal by nils måsén
• 🐛 [#635] bzip2 use explicit feature defs for vectorized memory move by Jackson Wood
• 🐛 [#645] tar create translated files in temp by nils måsén

Smaller changes:

• 🔨 [#604] Move the Password property from DeflaterOutputStream into ZipOutputStream by Richard Webb
• 🔨 [#625] Make BZip2Constants static instead of sealed by Richard Webb
• 🔨 [#626] make a couple of private functions static by Richard Webb

Other changes (not related to library code):

• 📚 [#648] zip fix ZipStrings typo by Friedrich von Never
• 🚨 add tests for tar path traversal by nils måsén
• ⚙️ add codeql analysis by nils måsén
• 🚨 [#636] Fix unstable tests and switch to dotcover by nils måsén
• 🚨 [#634] add an async version of the WriteZipOutputStream benchmark by Richard Webb
• ⚙️ [#628] Limit code coverage to windows CI by nils måsén
• 🚨 [#627] fix the expected/actual value ordering in unit tests by Richard Webb

v1.3.2

Another minor release, containing security fixes and smaller bugfixes.
Additionally, this version will have an additional target framework, .NET Standard 2.1, which will see some speed improvements when used in newer versions of .NET (Core), mainly in Bzip2.

Features

• [#611] Bzip input stream simple vectorization by Konrad Kruczyński
• [#351] Add support for Filename field in GZip by nils måsén

Smaller fixes and optimizations

• [#579] Implement very simple ReadAsync in ZipAESStream by Richard Webb
• [#587] Remove supported method checks from ZipEntry.CompressionMethod setter by Richard Webb
• [#593] Simplify DropPathRoot and fix out of bounds issue by nils måsén
• [#575] Replace uses of new T[0] with Array.Empty<T> by Richard Webb
• [#583] Restore entry times on FastZip extract by nils måsén
• [#517] Throw exception on Store+Descriptor entries by nils måsén
• [#578] Fix typos in the StreamDecodingException doc comments by Richard Webb
• [#577] Throw ZipException in ZipAESStream instead of generic Exception by Richard Webb
• [#510] Build the test bootstrapper app as netcoreapp3.1 instead of netcoreapp2.0 by Richard Webb
• [#546] Make pure private functions static by Richard Webb
• [#554] Skip CRC calculation for AES zip entries by nils måsén
• [#605] Suppress CA1707 warnings in the Constants classes by Richard Webb
• [#549] Add .NET Standard 2.1 target framework by Cédric Luthi

Other changes (not related to library code)

... (truncated)

Commits

• 1b1ab01 ci: include non-anno tags in version
• d21c998 ci: fix yaml typo
• a1423c4 ci: add manual dispatch and logging
• 641f292 update csproj for v1.3.3 release
• 5c3b293 fix: specialized tar extract traversal
• a0e96de test: add tests for tar path traversal
• 2b8ff8f update security policy
• cd5310f fix(bzip2): use explicit feature defs for vectorized memory move (#635)
• f04d973 ci: add codeql analysis
• 0cc20b4 docs(zip): fix ZipStrings typo (#648)
• 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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @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)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[pull-request-quantifier-deprecated]

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

---

Quantification details

Label      : Extra Small
Size       : +1 -1
Percentile : 0.8%

Total files changed: 1

Change summary by file extension:
.csproj : +1 -1

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

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
  • 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 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? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.