chore: remove redundant @Repository annotations and upgrade Spring Boot to 4.1.0

[Ludy87]

Description of Changes

This PR removes redundant @Repository annotations from Spring Data JPA repository interfaces and updates several core framework dependencies, primarily upgrading Spring Boot to 4.1.0.

What was changed

• Upgraded Spring Boot from 4.0.6 to 4.1.0.
• Updated Spring Security SAML from 7.0.5 to 7.1.0.
• Updated the dependency-license-report Gradle plugin from 3.1.2 to 3.1.4.
• Removed unnecessary @Repository annotations and related imports from all Spring Data JPA repository interfaces across the proprietary and saas modules.
• Updated comments and test assertions to refer to "repository interfaces" instead of "@Repository interfaces".
• Added forced dependency versions for:
  • org.apache.santuario:xmlsec:4.0.4
  • com.google.guava:guava:${guavaVersion}
• Added a getEnv() Gradle helper that logs relevant security and build environment variables during the build process.

Why the change was made

• Spring Data JPA automatically detects repository interfaces extending JpaRepository, making explicit @Repository annotations unnecessary.
• Upgrading to Spring Boot 4.1.0 and related dependencies keeps the project aligned with the latest framework improvements, bug fixes, and security updates.
• Explicit dependency resolution helps avoid version conflicts introduced through transitive dependencies.
• Additional environment logging simplifies troubleshooting of build and CI configuration.

---

Checklist

General

• I have read the Contribution Guidelines
• I have read the Stirling-PDF Developer Guide (if applicable)
• I have read the How to add new languages to Stirling-PDF (if applicable)
• I have performed a self-review of my own code
• My changes generate no new warnings

Documentation

• I have updated relevant docs on Stirling-PDF's doc repo (if functionality has heavily changed)
• I have read the section Add New Translation Tags (for new translation tags only)

Translations (if applicable)

• I ran scripts/counter_translation.py

UI Changes (if applicable)

• Screenshots or videos demonstrating the UI changes are attached (e.g., as comments or direct attachments in the PR)

Testing (if applicable)

• I have run task check to verify linters, typechecks, and tests pass
• I have tested my changes locally. Refer to the Testing Guide for more details.

[aikido-pr-checks]

Query logic conflicts with its documented behavior: coalesce(p.sortOrder, 0) makes null and 0 equivalent, so null sortOrder rows are not guaranteed to sort first.

Show fix

Suggested change

	+ " p.teamId = :teamId) order by coalesce(p.sortOrder, 0) asc, p.id asc")
	List<PolicyEntity> findByTeam(@Param("teamId") Long teamId);
	/** All policies in run order — used when team scoping is off (login-disabled). */
	@Query("select p from PolicyEntity p order by coalesce(p.sortOrder, 0) asc, p.id asc")
	+ " p.teamId = :teamId) order by p.sortOrder nulls first, p.id asc")
	List<PolicyEntity> findByTeam(@Param("teamId") Long teamId);
	/** All policies in run order — used when team scoping is off (login-disabled). */
	@Query("select p from PolicyEntity p order by p.sortOrder nulls first, p.id asc")

Details

✨ AI Reasoning
​The code is trying to define stable run ordering for team policies and documents that policies with no sort value come first. However, the ordering expression converts null to 0 before sorting. That means records with null and records with sortOrder = 0 are treated identically and then ordered only by id, so null-valued rows are not guaranteed to come first. This creates a concrete mismatch between the stated behavior and actual query semantics.

_{Reply @AikidoSec feedback: [FEEDBACK] to get better review comments in the future.
Reply @AikidoSec ignore: [REASON] to ignore this issue.
More info}

[stirlingbot]

✅ Backend License Check Passed

All backend dependencies have valid and allowed licenses.

The backend license report has been updated successfully.

[github-actions]

🚀 V2 Auto-Deployment Complete!

🔗 Direct Test URL (non-SSL) http://54.175.155.236:6930

🧩 Admin portal included - try it at http://54.175.155.236:6930/portal.

This deployment will be automatically cleaned up when the PR is closed.

🔄 Auto-deployed for approved V2 contributors.