[JS] kill chromium service on quit

[gravityvi]

Thanks for contributing to Selenium!
A PR well described will help maintainers to quickly review and merge it

Before submitting your PR, please check our contributing guidelines.
Avoid large PRs, help reviewers by making them as simple and short as possible.

Description

Motivation and Context

• fixes [🐛 Bug]: chromedriver service is not killed  #10795

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)

Checklist

• I have read the contributing document.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.
• I have added tests to cover my changes.
• All new and existing tests passed.

[diemol]

This is not the right solution because of #10499

The ideal solution is to start a driver per session, and not a single driver for all sessions.

[gravityvi]

removed setDefaultService as we want one service per instance it doesn't make sense to use same service across all instances of drivers and modified getDefaultService to return a new Driver Service instance

[AutomatedTester]

I think this looks fine, I am not sure where the setDefaultService command was used in a public setting or why one would use.

I won't merge as @diemol might have a different view of things to me

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[diemol]

Looks good to me, we just need to be responsive in case issues are raised.