Bump json5 and solidity-coverage in /ContractTests/token

[dependabot]

Removes json5. It's no longer used after updating ancestor dependency solidity-coverage. These dependencies need to be updated together.

Removes json5

Updates solidity-coverage from 0.2.2 to 0.8.2

Release notes

Sourced from solidity-coverage's releases.

0.8.2

What's Changed

• Set web3-utils dep to ^1.3.6 by @​MarkuSchick in sc-forks/solidity-coverage#744

New Contributors

• @​MarkuSchick made their first contribution in sc-forks/solidity-coverage#744

Full Changelog: sc-forks/solidity-coverage@v0.8.1...v0.8.2

0.8.1

What's Changed

• Bug fix: restore missing web3-utils dependency by @​cgewecke in sc-forks/solidity-coverage#743

Full Changelog: sc-forks/solidity-coverage@v0.8.0...v0.8.1

0.8.0

Hi!

⚠️ This version requires Hardhat >= 2.11.0 (Ethereum Merge)

New Features

A central focus of the 0.8.0 release is improving the coverage tool's branch detection.

Beginning with this version the following syntax is measured as a branch:

OR conditions

When a logical expression is composed with the || operator, both sides can be considered branches. To test the entire expression

if (a == 1 || a == 2)

... a must equal 1, 2 and neither of those values. (Thanks to Gnosis engineer @​rmeissner for proposing this in #175)

Ternary Conditionals

Long ago, when Solidity was 0.4, solidity-coverage treated ternary conditionals like regular if/else statements. Some language improvements v0.5 subsequently made this impossible. Now it's back...

Modifier Invocations

Solidity-coverage already covers the code within modifier definitions. However, each modifier invocation at the function level should really be considered its own branch. Some of the most critical logic in Solidity contracts is handled this way (ex: onlyOwner). Testing the pass/fail cases for each occurrence of these gates protects you from accidentally removing them during a refactor.

Because it's possible to write a modifier which performs a preparatory task and never reverts, there's a new option (modifierWhitelist) which allows you to exclude specific modifiers from branch measurement.

... (truncated)

Changelog

Sourced from solidity-coverage's changelog.

Changelog

0.8.1 / 2022-09-06

• Restore web3-utils (sc-forks/solidity-coverage#743)

0.8.0 / 2022-09-05

• See release notes at: https://github.com/sc-forks/solidity-coverage/releases/tag/v0.8.0

0.7.21 / 2022-04-24

• Add support for UncheckedStatement blocks (sc-forks/solidity-coverage#712)
• Lazy load hardhat plugin resources (sc-forks/solidity-coverage#711)

0.7.20 / 2022-02-15

• Remove early V7 Truffle patches (sc-forks/solidity-coverage#693)

0.7.19 / 2022-02-09

• Update solidity-parser/parser to 0.14.0 - supports solidity user-defined types (sc-forks/solidity-coverage#689)

0.7.18 2022-01-17

• Add solcOptimizerDetails option to help workaround "stack too deep" errors (sc-forks/solidity-coverage#683)
• Add __SOLIDITY_COVERAGE_RUNNING variable on global HH env for identifying solidity-coverage task from other tasks (sc-forks/solidity-coverage#682)
• Fix hardhat_reset (sc-forks/solidity-coverage#667)
• Add new hook and make temporary contracts directory configurable (sc-forks/solidity-coverage#664)
• Use internal visibility for fn level hash method defs (sc-forks/solidity-coverage#660)

0.7.16 / 2021-03-04

• Update @​solidity-parser/parser to ^0.12.0 (and support Panic keyword in catch clauses) (sc-forks/solidity-coverage#621)

0.7.15 / 2021-02-16

• Fix ctrl-c not exiting on Hardhat (sc-forks/solidity-coverage#616)
• Fix bug instrumentation bug w/ "pragma abicoder v2" (sc-forks/solidity-coverage#615)
• Update changelog: v0.7.14

0.7.14 / 2021-01-14

• Support file scoped function definitions for solc >= 0.7.4
• Upgrade @​solidity-parser/parser to v0.11.0

0.7.13 / 2020-12-03

• Use default artifact paths for hardhat >= 2.0.4 (Fixes hardhat-deploy bug)

... (truncated)

Commits

• See full diff 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

You can disable automated security fix PRs for this repo from the Security Alerts page.