Add Release Automation via GitHub Actions, Gradle Build Integration, and New Fake Player Multiplier

[Kykzuu]

Overview

This pull request introduces several significant updates to the project:

1. GitHub Actions for Automated Releases:

   • Added GitHub Actions workflows to automate the release process. This will help streamline our deployment pipeline and ensure consistent release practices.

2. Gradle Build Configuration:

   • Integrated Gradle for building the project and generating the JAR files. This provides a standardized build process and simplifies project management.

3. New Fake Player Multiplication Option:

   • Implemented a new feature for multiplying fake players. This allows for increased customization of fake player counts, improving the flexibility of the fake player system.

Changes

• Added GitHub Actions configuration files for release automation.
• Updated project build system to use Gradle, including configuration for JAR building.
• Enhanced the fake player system with an option to multiply player counts.

Benefits

• Automated Releases: Reduces manual effort and potential errors in the release process.
• Consistent Builds: Ensures reliable and reproducible builds with Gradle.
• Enhanced Functionality: Provides greater control over fake player numbers

[linsaftw]

Why gradle if we already have a maven pom? Maybe integrate automated builds with maven instead?

[sprytex]

Why gradle if we already have a maven pom? Maybe integrate automated builds with maven instead?

Why old maven