Configure dependabot to track NPM dependencies

[Zerpet]

Proposed Changes

This commit configures Dependabot to track and update NPM dependencies in selenium/package.json.

Key changes include:

• Daily updates for main, v4.2.x, v4.1.x, and v4.0.x branches.
• A 3-day cooldown for minor and major version updates.
• Grouping of minor and patch releases into a single pull request.

Types of Changes

What types of changes does your code introduce to this project?
Put an x in the boxes that apply

• Bug fix (non-breaking change which fixes issue #NNNN)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause an observable behavior change in existing systems)
• Documentation improvements (corrections, new content, etc)
• Cosmetic change (whitespace, formatting, etc)
• Build system and/or CI

Further comments

No need to backport. Dependabot uses only the main branch for its configuration.

[Zerpet]

Wait for @MarcialRosales review. IIRC, Marcial had an opinion about automating NPM dependencies.

[MarcialRosales]

We can go ahead with this bot. If it turns out to cause more trouble than good we can revert it. But it makes sense to do it as I only upgrade the dependencies when I cannot run the tests locally because the chromedriver cannot talk to the local chrome.