Validate HBase timestamp ranges during option parsing

Timestamp constraints were checked only when `HbaseClient` created a scan. Invalid negative, zero-end, equal, or reversed ranges could pass factory validation and fail later in the runtime path.

Added option-rule constraints for a non-negative start, a positive configured end, and `start_timestamp < end_timestamp`, while retaining runtime checks for direct or programmatic client construction and aligning English and Chinese documentation.

• Moves configuration errors to the earliest validation boundary and gives users faster, clearer feedback.
• Keeps defensive runtime validation for callers that bypass the connector factory.
• Aligns executable constraints, documentation, and edge-case coverage across both supported documentation languages.

• Added factory tests for omitted, partial, valid, negative, zero, minimum, equal, and reversed timestamp ranges.
• All 43 HBase connector tests passed in focused verification.
• Received approvals from three maintainers; both authored commits and the upstream merge commit are GitHub-verified.