Add support for multiline query formatting in Query annotations

[catturtle123]

This PR addresses issue #1726

Summary

• Default Data Query Style Change: Changed the default query generation style to compact (single line) to ensure broader compatibility across Java versions.

• Architectural Refinement (Interface Separation): Decoupled the query formatting logic by introducing the QueryFormatter interface with dedicated implementations (JpqlQueryFormatter, MongoQueryFormatter). This allows for repository-specific formatting strategies.

• Robust String Escaping & Formatting:

• Integrated StringEscapeUtils.escapeJava() to safe-guard generated queries against syntax errors.

• Multiline Indentation: Improved Text Block generation by adding proper indentation/alignment to ensure the generated query is visually consistent with the surrounding Java code.

• Configuration & Fallback: Updated logic to use compact and multiline keywords from UserSettings. Implemented a fallback mechanism that defaults to compact and triggers a log.warn for invalid or null inputs.

Key Changes

• Refactoring & Logic:

• QueryFormatter.java, JpqlQueryFormatter.java, MongoQueryFormatter.java: Separated formatting logic into an interface-based structure.

• BootJavaConfig.java: Updated style selection and added validation/fallback logic.

• DataRepositoryAotMetadataCodeLensProvider.java: Refactored to prioritize safety and proper indentation.

• Test Suite Updates:

• QueryMethodCodeActionProviderJpaTest.java & QueryMethodCodeActionProviderMongoDbTest.java: Updated to verify the output specifically for the compact style.

• DataRepositoryAotMetadataCodeLensProviderTest.java: Added comprehensive test cases for both compact and multiline styles, verifying correct indentation.

Resolved Issues

• Fixed Syntax Errors: Resolved IndexOutOfBoundsException by properly escaping special characters.
• Visual Alignment: Multiline queries now include appropriate leading spaces, improving the aesthetics of the generated code.
• Error Resilience: Prevents IDE tool failure by falling back to a safe default when configuration is missing or malformed.

Discussion Points

• Test Coverage Asymmetry: Currently, DataRepositoryAotMetadataCodeLensProviderTest provides full coverage for both styles. However, QueryMethodCodeActionProviderJpaTest and QueryMethodCodeActionProviderMongoDbTest are currently limited to verifying the compact style. Should I expand these two classes to include multiline test cases as well to maintain consistency?
• Fallback Strategy: Is the use of log.warn followed by a fallback to compact an acceptable approach for handling unexpected user configuration values? (Silent fallback to compact for null cases (no log.warn).)

Test