feat(zigbee): add Rti-Tek STHZB humidity sensor

[QuAnnan2019]

Type of Change

• WWST Certification Request
  • I have reviewed the README.md file
  • I have reviewed the CODE_OF_CONDUCT.md file
  • I have signed the CLA
  • I plan on entering a WWST Certification Request or have entered a request through the WWST Certification console at developer.smartthings.com
• Bug fix
• New feature
• Refactor

Checklist

• I have performed a self-review of my code
• I have commented my code in hard-to-understand areas
• I have verified my changes by testing with a device or have communicated a plan for testing
• I am adding new behavior, such as adding a sub-driver, and have added and run new unit tests to cover the new behavior

Description of Change

Adds manufacturer fingerprint support for the Rti-Tek STHZB Zigbee temperature and humidity sensor to the existing zigbee-humidity-sensor Edge driver.

The rtitek-sthzb profile exposes only SmartThings standard capabilities: temperature measurement, relative humidity measurement, battery, temperature alarm, and refresh. The driver reads and writes the device's FD22 manufacturer-specific cluster internally, but does not expose private-cluster data or Custom Capabilities to users.

Summary of Completed Tests

• Local Lua integration tests: 69/69 passed for zigbee-humidity-sensor, including 9 Rti-Tek STHZB tests
• Lua syntax validation: luac -p passed for the Rti-Tek sub-driver
• CLI packaging, channel assignment, and Hub installation completed
• Real Hub validation: temperature, humidity, battery, refresh reads, FD22 configuration reads, C/F device-display unit, calibration values, temperature alarm state mapping, and alarm-limit writes
• Regression validation for paired alarm limits: the driver clamps invalid values before writing the device, including values submitted against stale device-side state

Device Preferences are platform-owned values and cannot be rewritten by an Edge driver; a clamped device value therefore cannot be reflected back into the Preference input UI. The driver preserves device-side safety by writing only valid threshold combinations.

SmartThings Console Test Suite execution and the WWST certification submission remain required before production publication.

[CLAassistant]

All committers have signed the CLA.