Fix jest-environment-node peer dep

[mskelton]

The current jest-environment-node peer dep is referencing a non-existant version.

[coveralls]

Pull Request Test Coverage Report for Build 1034432509

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.798%

---

Totals
Change from base Build 993176801:	0.0%
Covered Lines:	106
Relevant Lines:	109

---

💛 - Coveralls

[mxschmitt]

Has an issue occurred somehow?

[mskelton]

So, it will throw a peer dep warning when installing jest-environment-node 26.3.2 since it is too low a version, but 26.3.3 isn't available. Some of the projects I'm working on can't update to Jest 27 while we wait for other libraries to gain support for Jest 27.

It's not a deal breaker kind of issue, but since it is referencing a package version that doesn't exist, it feels like a good change to make.

[coveralls]

Pull Request Test Coverage Report for Build 1034432509

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.798%

---

Totals
Change from base Build 993176801:	0.0%
Covered Lines:	106
Relevant Lines:	109

---

💛 - Coveralls

[coveralls]

Pull Request Test Coverage Report for Build 1034432509

Warning: This coverage report may be inaccurate.

This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

• For more information on this, see Tracking coverage changes with pull request builds.
• To avoid this issue with future PRs, see these Recommended CI Configurations.
• For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• No unchanged relevant lines lost coverage.
• Overall coverage remained the same at 94.798%

---

Totals
Change from base Build 993176801:	0.0%
Covered Lines:	106
Relevant Lines:	109

---

💛 - Coveralls