Refactor Thread Creation to ThreadFactory for better Thread namings

[ByteExceptionM]

In this pull request, I've made a significant change to the way threads are created. Instead of using the default thread naming convention, which results in generic names like Thread-XX, I've implemented a ThreadFactory to assign meaningful names to threads.

This change is highly beneficial for several reasons:

Improved Debugging and Maintenance:
Named threads provide clear and informative identifiers, making it significantly easier to identify the purpose and origin of a specific thread during debugging and code maintenance. It reduces the ambiguity associated with generic thread names and simplifies the troubleshooting process.

Enhanced Logging and Monitoring:
When threads are assigned meaningful names, the logs and monitoring tools can display more informative and human-readable information. This is especially valuable in a multi-threaded Minecraft Servers, where tracking thread activity is crucial for performance optimization and issue identification.

My IDE has also refactored the imports, if this is a problem, let me know!

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.