Add Unlatch command and Unlatched status (Unbolt feature)

[HunsupJung]

Check all that apply

Type of Change

• WWST Certification Request
  • If this is your first time contributing code:
    • 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

To support the Unbolt feature

Summary of Completed Tests

[github-actions]

Duplicate profile check: Warning - duplicate profiles detected.
lock-unlatch.yml == lock.yml
lock-user-pin-schedule-unlatch.yml == lock-user-pin-schedule.yml
lock-user-pin-unlatch.yml == lock-user-pin.yml
lock-user-schedule-unlatch.yml == lock-user-schedule.yml
lock-user-unlatch.yml == lock-user.yml

[github-actions]

Invitation URL:
https://bestow-regional.api.smartthings.com/invite/Boj0AwxQP9MA

[github-actions]

Test Results

   64 files    401 suites   0s ⏱️
1 999 tests 1 996 ✅ 0 💤 3 ❌
3 439 runs  3 435 ✅ 0 💤 4 ❌

For more details on these failures, see this check.

Results for commit b002d61.

[github-actions]

File	Coverage
All files	89%	❌
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-lock/src/init.lua	91%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-lock/src/lock_utils.lua	98%	✅
/home/runner/work/SmartThingsEdgeDrivers/SmartThingsEdgeDrivers/drivers/SmartThings/matter-lock/src/new-matter-lock/init.lua	88%	❌

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against b002d61

[tpmanley]

I think unlatched needs to be added to enabledValues in all these new *-unlatch profiles

[tpmanley]

I believe supportedLockCommands needs to be set appropriately as well, either including unlatch or not, depending on whether the device supports the UBOLT feature