fix: glob backward compatibility

[kobenguyent]

Motivation/Description of the PR

• Description of this PR, which problem it solves
• Resolves #issueId (if applicable).

Applicable helpers:

• Playwright
• Puppeteer
• WebDriver
• REST
• FileHelper
• Appium
• TestCafe

Applicable plugins:

• allure
• autoDelay
• autoLogin
• customLocator
• pauseOnFail
• coverage
• retryFailedStep
• screenshotOnFail
• selenoid
• stepByStepReport
• stepTimeout
• wdio
• subtitles

Type of change

• 🔥 Breaking changes
• 🚀 New functionality
• 🐛 Bug fix
• 🧹 Chore
• 📋 Documentation changes/updates
• ♨️ Hot fix
• 🔨 Markdown files fix - not related to source code
• 💅 Polish code

Checklist:

• Tests have been added
• Documentation has been added (Run npm run docs)
• Lint checking (Run npm run lint)
• Local tests are passed (Run npm test)

[kobenguyent]

published as codeceptjs@3.7.0-beta.7 for testing.

[DavertMik]

I'm not sure if we use it correctly:

In 10-11 our glob = require('glob') probably won't work

https://github.com/isaacs/node-glob/blob/main/changelog.md#1000

[DavertMik]

I didn't test this notation, but we need to ensure we use compatible glob version

Also I'm concerned that we can actually use glob from v11 because of no named exports

[DavertMik]

@kobenguyent please change the notation where glob is used

so instead of

const glob = require('glob')

we would have

const { globSync }  = require('glob')

as it is recommended now in docs

I checked it works on 9 and 11 version