[grid] Remove GridShutdown test

[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

Remove GridShutdown test since Grid 4 has the functionality

Motivation and Context

Grid 3 :
GridRegistry is the central place of the Grid where each Node registers itself to the Hub. It assigns any new incoming request to the queue and maintains HTTP connections to the Node.
Hence, to control its lifecycle, correctly clean up the resources and stop threads, shutdown() method is used. It stops the queue, stops the request matching thread, stops all registered nodes and closes the HTTP client connections.

Grid 4 :
The current implementation for Grid 4 is very different. The fully distributed mode has 5 components. Each component runs as a netty server. The netty server implements a stop() method, that stops all its thread groups gracefully. Additionally, there are JVM hooks to shutdown any ongoing threads like the new session distributor thread, retry request session queue thread. The JVM hook also shuts down the async HTTP client to free up the resources. There are separate endpoints to drain a node which in turns frees up the resources. However, there is no single endpoint/method to be called that can explicitly shut down the entire grid since this is a security risk.

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]

Thank you, @pujagani!

[sonarcloud]

Kudos, SonarCloud Quality Gate passed!

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information