Update new-matter-lock driver

[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

1. Issue
   User is allowed to lock or unlock from the device card if door lock status is unlatched, but user is not allowed to do the same from Plugin.

2. Solution
   Add Visible Condition to the profiles that have unlatched status

3. Changes
   Add Visible Condition to the profiles that have unlatched status
   Add some profiles for unlatch feature

Summary of Completed Tests

[github-actions]

Duplicate profile check: Passed - no duplicate profiles detected.

[github-actions]

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

[github-actions]

Test Results

   64 files  ± 0    410 suites  ±0   0s ⏱️ ±0s
2 065 tests  -  2  2 065 ✅  -  2  0 💤 ±0  0 ❌ ±0 
3 536 runs   - 10  3 536 ✅  - 10  0 💤 ±0  0 ❌ ±0 

Results for commit ac1c841. ± Comparison against base commit d649f75.

This pull request removes 2 tests.

Handle Unlatch Operation event from Matter device.
Handle Unlatch command received from SmartThings.

♻️ This comment has been updated with latest results.

[github-actions]

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

Minimum allowed coverage is 90%

Generated by 🐒 cobertura-action against ac1c841

[hcarter-775]

Can you add a unit test to ensure the battery profiling works as expected for these new profiles?

[hcarter-775]

should we close this PR then? https://github.com/SmartThingsCommunity/SmartThingsEdgeDrivers/pull/1880/files

[HunsupJung]

@hcarter-775
Yes, I will close this PR.
#1880

[HunsupJung]

@hcarter-775
When I check the result of "Run driver tests", the error occurs as like below

    lua: .../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:287: expected comma
    stack traceback:
    	[C]: in function 'error'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:287: in method 'expect'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:537: in method 'parseInlineHash'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:347: in method 'parse'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:516: in method 'parseHash'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:351: in method 'parse'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:560: in method 'parseList'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:345: in method 'parse'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:516: in method 'parseHash'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:351: in method 'parse'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:516: in method 'parseHash'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:351: in method 'parse'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:516: in method 'parseHash'
    	.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:351: in function <.../Project/hub-core/lib/scripting-engine/lua_libs/yaml.lua:320>
    	(...tail calls...)
    	...lib/scripting-engine/lua_libs/integration_test/utils.lua:111: in function 'integration_test.utils.get_profile_definition'
    	...atter-lock/src/test/test_matter_lock_unlatch_battery.lua:72: in main chunk
    	[C]: in ?

As above error log, There's a problem that lua_libs doesn't support deviceConfig in profile files. We need to update lua_libs to solve this issue.
In my opinion, It would be better that we merge this PR first without additional unit test and then update unit test file after updating lua_libs.