Add "preferences" constant to ServiceLocator initialization

[palukku]

User description

Closes #14807

Steps to test

Mandatory checks

• I own the copyright of the code submitted and I license it under the MIT license
• I manually tested my changes in running JabRef (always required)
• [/] I added JUnit tests for changes (if applicable)
• [/] I added screenshots in the PR description (if change is visible to the user)
• [/] I described the change in CHANGELOG.md in a way that is understandable for the average user (if change is visible to the user)
• [/] I checked the user documentation: Is the information available and up to date? If not, I created an issue at https://github.com/JabRef/user-documentation/issues or, even better, I submitted a pull request updating file(s) in https://github.com/JabRef/user-documentation/tree/main/en.

---

PR Type

Bug fix

---

Description

• Add name and type parameters to preferences constant registration

• Ensures proper dependency injection of CliPreferences in ServiceLocator

• Fixes issue HTTP server endpoint /libraries/demo fails (returns HTTP 500 with HTML), breaking demo library retrieval. #14807 with preferences initialization

---

Diagram Walkthrough

flowchart LR
  A["ServiceLocator initialization"] -->|"addOneConstant"| B["preferences constant"]
  B -->|"with name & type"| C["CliPreferences injection"]

Loading

File Walkthrough

	Relevant files
Bug fix	Server.java Add name and type to preferences constant registration      jabsrv/src/main/java/org/jabref/http/server/Server.java Modified addOneConstant call for preferences to include name parameter "preferences" Added type parameter CliPreferences.class for proper type binding Ensures ServiceLocator can correctly inject preferences dependency +1/-1

---

[qodo-free-for-open-source-projects]

PR Compliance Guide 🔍

Below is a summary of compliance checks for this PR:

Security Compliance
🟢	No security concerns identified No security vulnerabilities detected by AI analysis. Human verification advised for critical code.
Ticket Compliance
🟡	🎫 #14807 🟢 Fix preferences dependency injection in ServiceLocator ⚪ Fix HTTP 500 error returned by /libraries/demo endpoint Ensure endpoint returns HTTP 200 OK status Ensure response Content-Type is application/json Ensure /tmp/demo.json contains valid demo JSON payload (approximately 10,975 bytes) Fix issue introduced by commit 636b37c from PR
Codebase Duplication Compliance
⚪	Codebase context is not defined Follow the guide to enable codebase context checks.
Custom Compliance
🟢	Generic: Comprehensive Audit Trails Objective: To create a detailed and reliable record of critical system actions for security analysis and compliance. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Meaningful Naming and Self-Documenting Code Objective: Ensure all identifiers clearly express their purpose and intent, making code self-documenting Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Robust Error Handling and Edge Case Management Objective: Ensure comprehensive error handling that provides meaningful context and graceful degradation Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Error Handling Objective: To prevent the leakage of sensitive system information through error messages while providing sufficient detail for internal debugging. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Secure Logging Practices Objective: To ensure logs are useful for debugging and auditing without exposing sensitive information like PII, PHI, or cardholder data. Status: Passed Learn more about managing compliance generic rules or creating your own custom rules
	Generic: Security-First Input Validation and Data Handling Objective: Ensure all data inputs are validated, sanitized, and handled securely to prevent vulnerabilities Status: Passed Learn more about managing compliance generic rules or creating your own custom rules

Compliance status legend

🟢 - Fully Compliant
🟡 - Partial Compliant
🔴 - Not Compliant
⚪ - Requires Further Human Verification
🏷️ - Compliance label

[subhramit]

approving based on discussion in call/chat

[qodo-free-for-open-source-projects]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Preserve interface bindings for dependency injection To avoid breaking dependency injection, use an overload of addOneConstant that preserves interface bindings while still adding a name to the preferences object. jabsrv/src/main/java/org/jabref/http/server/Server.java [98] -ServiceLocatorUtilities.addOneConstant(serviceLocator, preferences, "preferences", CliPreferences.class); +ServiceLocatorUtilities.addOneConstant(serviceLocator, preferences, "preferences"); Apply / Chat Suggestion importance[1-10]: 7 __ Why: The suggestion correctly identifies a subtle but important change in the dependency injection binding behavior, which could unintentionally break other parts of the application that rely on interface injection.	Medium
More