Implement typed errors

[Borewit]

This PR standardizes the error handling in the parsing module by introducing specific error classes, ensuring all thrown errors are of the type ParseErrorType. This enhancement improves type safety, clarity, and consistency across the codebase.

Changes Introduced

The following custom error classes have been introduced to represent specific parsing errors:

• CouldNotDetermineFileTypeError: Thrown when the parser cannot determine the file type.
• UnsupportedFileTypeError: Thrown when an unsupported file type is encountered.
• UnexpectedFileContentError: Thrown when the file content does not match the expected format.
• InternalParserError: Thrown in case of an internal error during parsing.

Unified Error Type

All the above error classes are grouped under a new union type, KindOfParseError, which provides a common structure for parsing-related

type KindOfParseError = 
  | CouldNotDetermineFileTypeError
  | UnsupportedFileTypeError
  | UnexpectedFileContentError
  | InternalParserError;

Each error class shares a common name property, which is useful for error identification and handling (switching).

PR suggestion provided by sponsor @schickling:

One thing that would be great as well would be to have improved error paths
Eg typed errors

@schickling can you please review?

[coveralls]

coverage: 97.078% (-0.01%) from 97.092%
when pulling 9bd97bd on custom-error-class
into 04fd5ee on master.

[Borewit]

Part of v10.3.0