chore(deps-dev): bump glob from 7.2.0 to 8.0.3

[dependabot[bot]]

Bumps glob from 7.2.0 to 8.0.3.

Changelog

Sourced from glob's changelog.

8.0

• Only support node v12 and higher
• \ is now only used as an escape character, and never as a path separator in glob patterns, so that Windows users have a way to match against filenames containing literal glob pattern characters.
• Glob pattern paths must use forward-slashes as path separators, since \ is an escape character to match literal glob pattern characters.
• (8.0.2) cwd and root will always be automatically coerced to use / as path separators on Windows, as they cannot contain glob patterns anyway, and are often supplied by path.resolve() and other methods that will use \ path separators by default.

7.2

• Add fs option to allow passing virtual filesystem

7.1

• Ignore stat errors that are not ENOENT to work around Windows issues.
• Support using root and absolute options together
• Bring back lumpy space princess
• force 'en' locale in string sorting

7.0

• Raise error if options.cwd is specified, and not a directory

6.0

• Remove comment and negation pattern support
• Ignore patterns are always in dot:true mode

5.0

• Deprecate comment and negation patterns
• Fix regression in mark and nodir options from making all cache keys absolute path.
• Abort if fs.readdir returns an error that's unexpected
• Don't emit match events for ignored items
• Treat ENOTSUP like ENOTDIR in readdir

4.5

• Add options.follow to always follow directory symlinks in globstar
• Add options.realpath to call fs.realpath on all results
• Always cache based on absolute path

... (truncated)

Commits

• d844b2c 8.0.3
• fc717ba [Refactor] use more explicit assert.ok
• d13cb06 8.0.2
• af4207b changelog updates re path separator handling
• 0049e9a always coerce cwd, root to '/' separated paths
• a8a3682 remove path-is-absolute
• 5630197 ci: test on node 18
• 7eab927 changelog updates
• 55ebc0b 8.0.1
• af3eb8a update tap to pull in fixed minimist
• 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)

[coveralls]

Coverage remained the same at 100.0% when pulling 214d79aeb6d8c9e8e9c25293bdaf6c672f3fa7ae on dependabot/npm_and_yarn/glob-8.0.3 into 400cb11514ecc1213bc6e81994ecb4d8a83c30a8 on master.

[github-actions[bot]]

:tada: This PR is included in version 6.0.1-beta.1 :tada:

The release is available on:

• npm package (@beta dist-tag)
• GitHub release

Your semantic-release bot :package::rocket:

[github-actions[bot]]

:tada: This PR is included in version 6.0.1 :tada:

The release is available on:

• npm package (@next dist-tag)
• GitHub release

Your semantic-release bot :package::rocket: