SIP2-313: Add automated patron blocks support to patron status/information response

[zakletskyi-epam]

Purpose

Patron status and patron information responses now reflect automated patron blocks (from /automated-patron-blocks) alongside existing manual blocks. Previously only manual blocks affected SIP2 patron status flags and screen messages

Approach

• Added getAutomatedBlocksByUserId() to FeeFinesRepository — fetches /automated-patron-blocks?query=userId==...; logs a warning and gracefully returns null on failure so a down endpoint never surfaces as a SIP2 error
• Both validPatron(PatronStatusRequest) and validPatron(PatronInformation) in PatronRepository now fetch manual and automated blocks in parallel via Future.all(), then merge the resulting EnumSet flags (union) and concatenate screen messages
• Block-to-flag mapping mirrors manual block logic: blockBorrowing → all 14 flags, blockRenewals → RENEWAL_PRIVILEGES_DENIED, blockRequests → HOLD_PRIVILEGES_DENIED + RECALL_PRIVILEGES_DENIED
• Tests: 3 new FeeFinesRepositoryTests, 7 new PatronRepositoryTests (including partial-block and merge scenarios), 1 new PatronStatusIT, 1 new PatronInformationIT

Changes Checklist

• API Changes: Document any API paths, methods, request or response bodies changed, added, or removed.
• Database Schema Changes: Indicate any database schema changes and their impact. Confirm that migration scripts were created.
• Interface Version Changes: Indicate any changes to interface versions.
• Interface Dependencies: Document added or removed dependencies.
• Permissions: Document any changes to permissions.
• Logging: Confirm that logging is appropriately handled.
• Unit Testing: Confirm that changed classes were covered by unit tests.
• Integration Testing: Confirm that changed logic was covered by integration tests.
• Manual Testing: Confirm that changes were tested on local or dev environment.
• NEWS: Confirm that the NEWS file is updated with relevant information about the changes made in this pull request.

Related Issues

SIP2-313

Learning and Resources (if applicable)

Discuss any research conducted during the development of this pull request. Include links to relevant blog posts, patterns, libraries, or addons that were used to solve the problem.

Screenshots (if applicable)

If this pull request involves any visual changes or new features, consider including screenshots or GIFs to illustrate the changes.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
99.0% Coverage on New Code
2.1% Duplication on New Code

See analysis details on SonarQube Cloud