Fix memory exhaustion when reading corrupted FPT memo files

[panel-sk]

Prevents the memo reader from attempting to allocate excessive memory when encountering corrupted FPT files.

Added a safety check to limit the maximum memo length to 100MB per column, preventing fatal memory errors (e.g., attempts to allocate ~1.9GB) during file processing.

[codecov-commenter]

Welcome to Codecov 🎉

Once you merge this PR into your default branch, you're all set! Codecov will compare coverage reports and display results in all future pull requests.

Thanks for integrating Codecov - We've got you covered ☂️

[panel-sk]

Sorry for spaming with unchecked commits. I'm little still learning how to work with Github. Test are fixed.

• Fix memory exhaustion when reading corrupted FPT memo files
• Replaced deprecated Code Climate test-reporter with Codecov for coverage reporting to fix persistent 404/download issues.
• Updated actions/checkout, actions/upload-artifact, and actions/download-artifact to v4.
• Ensured unique artifact naming to comply with upload-artifact@v4 requirements.
• Configured workflow to run on all branches for easier testing in forks.
• Set fail_ci_if_error to false for Codecov to allow tests to pass even without a token in fork environments.

[panel-sk]

@gam6itko Hello.

I encountered a critical issue where corrupted memo files (.fpt) caused the StreamWrapper to attempt reading excessive amounts of data, leading to a fatal memory exhaustion error.

Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 1932407120 bytes) in /var/www/html/vendor/hisamu/php-xbase/src/Stream/StreamWrapper.php on line 91
[2026-01-28 00:47:45] [ERROR] Fatal error: Allowed memory size of 1073741824 bytes exhausted (tried to allocate 1932407120 bytes) in /var/www/html/vendor/hisamu/php-xbase/src/Stream/StreamWrapper.php:91

When a memo field header is corrupted, the length value can be read as an extremely large integer. The current implementation attempts to allocate memory based on this value without validation.

I've implemented a safety guard that throws an Exception if a single memo field exceeds a 100MB threshold.

While FoxPro theoretically allows large files, a single memo entry exceeding 100MB is highly atypical for standard DBF use cases and almost certainly indicates file corruption. This limit prevents the PHP process from crashing the entire environment.

// Safety check: prevent reading corrupted/huge memo fields (max 100MB)
if ($memoLength[1] > 104857600) {
    throw new \Exception("Corrupted FPT file: memo field size {$memoLength[1]} bytes exceeds 100MB limit");
}

If 100MB is considered too restrictive for this library, I am open to making this value configurable or adjusting it based on your feedback.