Repo Cleanup and Readability Improvements

[CJCrafter]

It is hard for me to believe, but we are now 4 years into WeaponMechanics development (We started January 22nd, 2020). It's about time that this code base received a fresh coat of paint with all the things we have learned since we started, namely:

Gradle Changes

• [x] updating to Gradle 8.5
  • [x] update to shadowJar 8.1.1
  • [x] update to paperweight 1.5.11
• [x] Clean build.gradle.kts files
  • [x] Remove redundant name, version, and description variables
  • [x] Move all repositories {} calls to 1 central file in buildSrc
  • [x] Remove repositories that we do not use anymore (and comment which repositories correspond to which libs!)
  • [x] Use Kotlin extension functions for a condense format... less clutter
• [x] Add Maven Repository (Done in #384)
• [ ] Compatibility Changes
  • [x] Automatically load modules based on Regex expressions to avoid manual updates each MC update
  • [ ] Merge WeaponCompatibility and CoreCompatibility (Maybe?)
• [x] Kotlinize
  • [x] Add Kotlin JVM support to MechanicsCore
• [x] Add "dev mode" for new developers so they don't need to run BuildTools to contribute
  • (basically this just removes the older compatibility modules from being compiled)

Codebase Changes

• [ ] Add WeaponData class outlined in #388
• [ ] Add jetbrains @NotNull and @Nullable where appropriate.
• [x] Refactor NumberUtil to contain more math utilities, and follow better standards (Specifically in argument order)

Misc

• [x] Cleanup GitHub
  • [x] Improve README.md information
  • [x] Add contributing information
  • [x] Add premade Pull Request formats
  • [x] Add resourcepack to git for easier contributions? (Not the .zip files, an actual directory)
• [x] GitHub Actions
  • [x] Validate PR (run tests, check for vulnerabilities)
  • [ ] Auto update libs
  • [ ] Auto update README.md

[CJCrafter]

A note on Kotlin:

WeaponMechanics will likely never be fully converted over to Kotlin. While I plan on converting a few specific classes to Kotlin, it will likely stop there. The reason for NOT converting everything is this: maintainability. For example, the main purpose of this PR is to make it easier for all devs to contribute to WeaponMechanics.

So why am I adding Kotlin in the first place? Why am I converting a few classes over and not others? WeaponMechanicsPlus and ArmorMechanics are written in Kotlin. All my future JVM projects are written in Kotlin. I strongly believe that how Kotlin handles nullibility results in better code that is as fast as or even faster then typical Java code. So I want to make it easier for Kotlin devs to use WeaponMechanics.

[CJCrafter]

This is being merged, but the work is not entirely "done". We still need to update all plugins to use the new references, new methods. This is sortof a bummer, but my naming conventions were HORRIBLE 4 years ago.