Refined Exception Handling for Specific Error Cases in Tarfile Processing

Error handling patterns involve structuring code to catch and respond to exceptions in a way that accurately reflects the different failure modes and their implications. Instead of broadly catching all related errors, distinguishing between specific exceptions allows for more precise control flow and better resilience, especially in complex I/O operations like archive processing.

In this PR, the fix targets how `tarfile.open()` handles PAX archives with only global headers and no regular files. Previously, an `EOFHeaderError` raised after reading the global header was caught under a generic `HeaderError` clause and converted into a fatal `SubsequentHeaderError`, causing the open operation to fail incorrectly. The change introduces a separate catch for `EOFHeaderError` before the generic handler, allowing it to propagate normally for global headers (type `XGLTYPE`), which signals a legitimate end of archive rather than an error. For extended headers (`XHDTYPE`), the error is still treated as fatal, preserving the intended logic. This nuanced exception handling fixes the bug without compromising error detection elsewhere.

Understanding and applying precise error handling patterns prevents misclassification of normal conditions as errors, improving robustness and user experience. It also makes the codebase easier to maintain and extend by clearly expressing the intended control flow for different failure scenarios.

Review the exception handling in `TarInfo._proc_pax()` as modified in this PR. How would you extend this pattern if a new header type required a different EOF handling behavior? Write a small code snippet or pseudocode showing how you would structure the exception handling to accommodate this new case without disrupting existing logic.