Enforce seekable, readable and writable on streams

[adamhathcock]

Inspired by #1296

This pull request refactors validation logic for stream parameters throughout the archive and reader factory classes. The main improvement is replacing scattered null and capability checks with centralized extension methods, specifically RequireReadable() and RequireSeekable(). This change ensures consistency, reduces code duplication, and improves readability and maintainability.

The most important changes are:

Stream Validation Refactoring:

• Replaced all usages of NotNull and explicit CanRead/CanSeek checks with the new RequireReadable() and RequireSeekable() extension methods for both single and multi-stream parameters in archive and reader factory methods. This affects methods in ArchiveFactory, GZipArchive.Factory, RarArchive.Factory, SevenZipArchive.Factory, TarArchive.Factory, ZipArchive.Factory, and all corresponding reader factories. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22] [23] [24] [25] [26] [27] [28] [29] [30] [31]

Consistency Improvements:

• Ensured that all factory methods for opening archives and readers (sync and async) now consistently validate that streams are readable and, where required, seekable, using the same extension methods. This eliminates subtle bugs and inconsistent error handling across formats. (All references above)

Simplification of Method Bodies:

• Removed repetitive null and capability checks, as well as redundant exception throwing code, in favor of the new extension methods, resulting in cleaner and more maintainable method implementations. (All references above)

This refactoring centralizes stream validation, making the codebase easier to maintain and less error-prone.