[Batch] fix large size validation

[scarlet25151]

Pull Request Description

[Please provide a clear and concise description of your changes here]
Fix the Frontend error when validating large dataset.
when submitting large file, the validation will failed and return error:

after the fix:

Important: Before submitting, please complete the description above and review the checklist below.

---

Contribution Guidelines (Expand for Details)

We appreciate your contribution to aibrix! To ensure a smooth review process and maintain high code quality, please adhere to the following guidelines:

Pull Request Title Format

Your PR title should start with one of these prefixes to indicate the nature of the change:

• [Bug]: Corrections to existing functionality
• [CI]: Changes to build process or CI pipeline
• [Docs]: Updates or additions to documentation
• [API]: Modifications to aibrix's API or interface
• [CLI]: Changes or additions to the Command Line Interface
• [Misc]: For changes not covered above (use sparingly)

Note: For changes spanning multiple categories, use multiple prefixes in order of importance.

Submission Checklist

• PR title includes appropriate prefix(es)
• Changes are clearly explained in the PR description
• New and existing tests pass successfully
• Code adheres to project style and best practices
• Documentation updated to reflect changes (if applicable)
• Thorough testing completed, no regressions introduced

By submitting this PR, you confirm that you've read these guidelines and your changes align with the project's contribution standards.

[gemini-code-assist]

Code Review

This pull request introduces chunked JSONL file parsing (parseJsonlFile) to prevent UI freezing and high memory usage when validating large batch files in the browser. It includes options for timeouts, chunk sizes, and yielding to the main thread, along with corresponding unit tests. The review feedback correctly identifies a potential memory leak and UI thread blocking issue in CreateJob.tsx where a large file's full parse could be cached in the React state during job creation, and suggests removing this state update.