[CHORE] Update all Java source file usages of UnravelDocsResponse to XtractionResponse

[aniebietafia]

Problem

After renaming the class (Issue 4), every Java file that references UnravelDocsResponse needs to be updated. Static analysis identified usages in at minimum:

• All controllers (AdminController, AuthController, DocumentController, UserController, TeamController, CreditPackController, and more)
• All service interfaces that return the wrapper type
• All service implementation files
• All test files

Failure to update these produces compilation errors that block the entire build.

Proposed Solution

Perform a codebase-wide IDE refactor rename on the class (not a raw find-and-replace) to safely update all type references, import statements, and generic usages simultaneously.

User Stories

• As a developer, I want all Java source files to compile against XtractionResponse<T> so the project builds cleanly and consistently reflects the Xtraction brand.

Acceptance Criteria

• mvn compile passes with zero errors
• grep -r "UnravelDocsResponse" src/ returns zero results
• All controller return types use XtractionResponse<T>
• All service interface signatures use XtractionResponse<T>
• All test files updated

Proposed Technical Details

Use IntelliJ IDEA's Rename Refactor (Shift+F6 on the class name) — this updates:

• import statements
• Type declarations in method signatures
• Generic usages like ResponseEntity<UnravelDocsResponse<UserData>>
• new UnravelDocsResponse<>() instantiation expressions
• Javadoc @return type mentions

After the IDE refactor, run a final grep to confirm no stragglers remain:

grep -r "UnravelDocsResponse" src/

Tasks

• Confirm Issue 4 is merged before starting
• Run IDE rename refactor on XtractionResponse class across all modules
• Run grep -r "UnravelDocsResponse" src/ to catch any missed occurrences
• Run mvn clean compile and verify zero errors
• Run mvn test and verify no test failures related to the rename

Open Questions / Considerations

• Coordinate with all open PRs to avoid large rebase conflicts — this is a wide-impact change.
• This change should be done in a dedicated PR that touches only the rename, not mixed with feature work.