Bump babel-jest from 25.2.6 to 27.0.5 in /backend

Created by: dependabot-preview[bot]

Bumps babel-jest from 25.2.6 to 27.0.5.

Release notes

Sourced from babel-jest's releases.

27.0.5

Features

• [@jest/fake-timers] Flush callbacks scheduled with requestAnimationFrame every 16ms when using legacy timers. (#11523)
• [pretty-format] Use globalThis (with polyfill if required) to bring support for esbuild's browser bundling mode (#11569

Fixes

• [jest-core] Support special characters like @, + and () on Windows with --findRelatedTests (#11548)
• [@jest/fake-timers] Do not add setImmediate and clearImmediate if they do not exist in the global environment (#11599)
• [@jest/reporters] Allow node-notifier@10 as peer dependency (#11523)
• [@jest/reporters] Update v8-to-istanbul (#11523)

27.0.4

Fixes

• [jest-config, jest-resolve] Pass in require.resolve to resolvers to resolve from correct base (#11493)

27.0.3

Fixes

• [jest-config] require.resolve on default test sequencer and test environment (#11482)
• [jest-mock] Fixed fn and spyOn exports (#11480)

27.0.2

Features

• [jest-circus] Add some APIs to make it easier to build your own test runner
• [jest-reporters] Expose the getResultHeader util (#11460)
• [jest-resolver] Export resolve* utils for different Jest modules (#11466)
• [@jest/test-result] Export Test, TestEvents and TestFileEvent (#11466)

Fixes

• [jest-circus] Add missing slash dependency (#11465)
• [jest-circus, @jest/test-sequencer] Remove dependency on jest-runner (#11466)
• [jest-config] Resolve config.runner to absolute path (#11465)
• [jest-config] Make sure to support functions as config (#11475)
• [jest-core] Do not warn about DNSCHANNEL handles when using the --detectOpenHandles option (#11470)
• [jest-runner] Remove dependency on jest-config (#11466)
• [jest-worker] Loosen engine requirement to >= 10.13.0 (#11451)

27.0.1

Fixes

• [jest-environment-jsdom] Bump version of JSDOM to avoid deprecated request package (#11442)

27.0.0

Blog post

... (truncated)

Changelog

Sourced from babel-jest's changelog.

27.0.5

Features

• [@jest/fake-timers] Flush callbacks scheduled with requestAnimationFrame every 16ms when using legacy timers. (#11523)
• [pretty-format] Use globalThis (with polyfill if required) to bring support for esbuild's browser bundling mode (#11569

Fixes

• [jest-core] Support special characters like @, + and () on Windows with --findRelatedTests (#11548)
• [@jest/fake-timers] Do not add setImmediate and clearImmediate if they do not exist in the global environment (#11599)
• [@jest/reporters] Allow node-notifier@10 as peer dependency (#11523)
• [@jest/reporters] Update v8-to-istanbul (#11523)

27.0.4

Fixes

• [jest-config, jest-resolve] Pass in require.resolve to resolvers to resolve from correct base (#11493)

27.0.3

Fixes

• [jest-config] require.resolve on default test sequencer and test environment (#11482)
• [jest-mock] Fixed fn and spyOn exports (#11480)

27.0.2

Features

• [jest-circus] Add some APIs to make it easier to build your own test runner
• [jest-reporters] Expose the getResultHeader util (#11460)
• [jest-resolver] Export resolve* utils for different Jest modules (#11466)
• [@jest/test-result] Export Test, TestEvents and TestFileEvent (#11466)

Fixes

• [jest-circus] Add missing slash dependency (#11465)
• [jest-circus, @jest/test-sequencer] Remove dependency on jest-runner (#11466)
• [jest-config] Resolve config.runner to absolute path (#11465)
• [jest-config] Make sure to support functions as config (#11475)
• [jest-core] Do not warn about DNSCHANNEL handles when using the --detectOpenHandles option (#11470)
• [jest-runner] Remove dependency on jest-config (#11466)
• [jest-worker] Loosen engine requirement to >= 10.13.0 (#11451)

27.0.1

Fixes

... (truncated)

Commits

• dafa473 v27.0.5
• 7ca8a22 v27.0.2
• 2cb20e9 v27.0.1
• be16e47 v27.0.0
• e2eb9ae v27.0.0-next.11
• 6f44529 v27.0.0-next.10
• d836f33 v27.0.0-next.9
• d7ba503 v27.0.0-next.8
• 28c763e v27.0.0-next.7
• 974d2f2 v27.0.0-next.6
• 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)
• @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
• @dependabot badge me will comment on this PR with code to add a "Dependabot enabled" badge to your readme

Additionally, you can set the following in your Dependabot dashboard:

• Update frequency (including time of day and day of week)
• Pull request limits (per update run and/or open at any time)
• Out-of-range updates (receive only lockfile updates, if desired)
• Security updates (receive only security updates, if desired)