Bump sinon from 5.0.7 to 12.0.1 in /build

[dependabot]

Bumps sinon from 5.0.7 to 12.0.1.

Changelog

Sourced from sinon's changelog.

12.0.1

• 3f598221 Fix issue with npm unlink for npm version > 6 (Carl-Erik Kopseng)

  'npm unlink' would implicitly unlink the current dir until version 7, which requires an argument

• 51417a38 Fix bundling of cjs module (#2412) (Julian Grinblat)

  • Fix bundling of cjs module >
  • Run prettier

Released by Carl-Erik Kopseng on 2021-11-04.

12.0.0

• b20ef9e4 Upgrade to fake-timers@8 (Carl-Erik Kopseng). This is potentially breaking, but should not be, as the breaking change deals with the Node timer object created by fake timers.
• eba42cc3 Enable esm named exports (#2382) (Julian Grinblat)
• b0cf5448 Spelling (#2398) (Josh Soref)
• e78a6706 Make calledWith() assertions idempotent (#2407) (Joel Bradshaw)
• 2814c0a2 Generate CHANGES.md using @​studio/changes (Morgan Roderick)

  This will bring us closer to having the same release process as the other @sinonjs packages.

• 2d5d6ad4 Run tests in Node 16 in GitHub Actions (Morgan Roderick)

Released by Carl-Erik Kopseng on 2021-11-03.

11.1.2

• Upgrade @​sinonjs/fake-timers to latest, see https://github.com/sinonjs/fake-timers/blob/master/CHANGELOG.md#712--2021-05-28
• Copy over accessor properties to target object #2387

11.1.1

• Fix #2379 by using v7 of supports-color

11.1.0

• Add sinon.promise() implementation (#2369)
• Set wrappedMethod on getters/setters (#2378)
• [Docs] Update fake-server usage & descriptions (#2365)

... (truncated)

Commits

• 09039d7 12.0.1
• 3f59822 Fix issue with npm unlink for npm version > 6
• 51417a3 Fix bundling of cjs module (#2412)
• 14b4f5e Remove Sauce Labs badge
• 68a7cc0 Fix prettier error
• 5167e7d Update docs/changelog.md and set new release id in docs/_config.yml
• fedeebf Add release documentation for v12.0.0
• 0cf9235 update file path
• dfa4ecb update scriptname
• d97a1ef Rename
• 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)

[MichaIng]

About the jsunit error: #28264 (comment)

[dependabot]

Dependabot tried to update this pull request, but something went wrong. We're looking into it, but in the meantime you can retry the update by commenting @dependabot rebase.

[MichaIng]

Obsolete as of: #30718

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.