Add vid/pid of the Schlage Sense Pro to new-matter-lock

[HunsupJung]

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

Summary of Completed Tests

[github-actions]

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

[github-actions]

Test Results

   71 files    483 suites   0s ⏱️
2 497 tests 2 494 ✅ 0 💤 3 ❌
4 286 runs  4 283 ✅ 0 💤 3 ❌

For more details on these failures, see this check.

Results for commit 595f910.

♻️ This comment has been updated with latest results.

[github-actions]

File	Coverage
All files	72%	❌
/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	65%	❌

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against 595f910

[nickolas-deboom]

The DCL lists 0x3800 for the Schlage Sense Pro - is this pid correct or is this a different model?

[nickolas-deboom]

Suggested change

	{0x1236, 0xa538}, -- Kwikset Aura Reach
	{0x1236, 0xa538}, -- Schlage Sense Pro

[HunsupJung]

You are right. Thank you for checking.

[Kwang-Hui]

looks good to me