[grid] Consider max-session value while selecting the slot and identifying Node capacity

[pujagani]

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

Consider max-session value while selecting the slot and identifying Node capacity

Motivation and Context

Node allows configuring max-session value. In the current implementation, to ensure Grid is not underutilized, multiple threads are used to reserve a slot and create the session. As a result, multiple sessions are created simultaneously which often exceeds the max-session value and disregards it. To avoid overloading the machine, it is crucial that the max-session value is considered. The changes fix this by checking for that the current number of sessions do not exceed the max-session value during slot selection.

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.

[sonarcloud]

SonarCloud Quality Gate failed.   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

0.0% Coverage
0.0% Duplication

[shs96c]

Looks great. Thank you, @pujagani!