drivers: Standardize continuous/one-shot mode method naming.

[nedseb]

Problem

Continuous and one-shot mode methods use inconsistent names across drivers.

Driver	Set continuous	Set one-shot	Trigger	Read one-shot
wsen-hids	set_continuous_mode(odr)	set_one_shot_mode()	trigger_one_shot()	read_one_shot()
wsen-pads	set_continuous(odr)	(implicit via power_down())	trigger_one_shot()	read_one_shot()
hts221	setODR(odr)	(none)	(none, PR #68 adds trigger_one_shot())	(none)
lis2mdl	set_mode("continuous")	set_mode("single")	(none)	(none)

Proposed convention

• set_continuous(odr=...): start continuous measurements at given rate
• trigger_one_shot(): trigger a single conversion (sensor must be in power-down/one-shot mode)
• read_one_shot(): trigger + wait + return data
• No separate set_one_shot_mode() needed if trigger_one_shot() handles it internally

wsen-hids and wsen-pads are already close to this convention.

Drivers to update

• hts221: add set_continuous(odr) wrapper, keep setODR() as legacy alias
• lis2mdl: add set_continuous(odr) and trigger_single() / trigger_one_shot()
• wsen-pads: set_continuous() already compliant
• wsen-hids: set_continuous_mode() → set_continuous() for consistency with wsen-pads

Dependencies

• Blocked by drivers: Migrate camelCase public methods to snake_case. #82 (camelCase → snake_case must happen first, e.g. setODR)
• Related to drivers: Standardize power on/off method naming. #76 (power_on/power_down — power-down is often the prerequisite for one-shot mode)

[semantic-release-updater]

🎉 This issue has been resolved in version 0.0.2 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀