Refactor ranking logic and enhance user statistics features

[ZayrexDev]

This pull request introduces several important updates and improvements to both the documentation and the codebase, primarily focusing on command naming consistency, enhanced API flexibility, and improved maintainability. The changes align the code and documentation with the new /bp (best performance) command, replace legacy /bo (best of) references, and generalize API methods to use explicit IDs instead of shortcut targets where appropriate.

Documentation and Command Consistency Improvements:

• Updated all references in README.md from /bo (best of) to /bp (best performance) for command names, arguments, and usage examples, ensuring consistency between documentation and code. Also revised related shortcut query examples and explanations. [1] [2]
• Clarified and expanded shortcut query syntax in the documentation to support new range and player-specific queries, and updated the description of debugging command permissions. [1] [2]
• Fixed oStella upstream data service link in README.md.
• Removed outdated or redundant statistics description from the documentation for clarity.

API and Codebase Refactoring:

• Refactored API methods in APIHelper.java to use explicit beatmap/beatmapset/score IDs in method signatures instead of ShortcutTarget where possible, improving clarity and reducing ambiguity. This includes changes to methods for fetching beatmaps, beatmapsets, backgrounds, and score details. [1] [2] [3] [4] [5] [6] [7]
• Added support for specifying a starting index (start) in best and recent score API queries, enabling range-based score retrieval for /bp and /rs commands. [1] [2]
• Updated macro type handling throughout the API to recognize /bp in addition to /bo, ensuring correct query formation and data retrieval. [1] [2]

Other Enhancements:

• Added NoticeStore.initialize() to the application startup sequence for improved notification handling. [1] [2]
• Bumped the project version from 1.11.6 to 1.12.0 in pom.xml.

These changes collectively improve the usability, maintainability, and clarity of both the documentation and the codebase, preparing the project for future enhancements and reducing user confusion.