ESP32: Add fixes for lock-app

[sweetymhaiske]

Problem

• Add missing fixes for lock-app ESP32.

Change overview

1. Added missing cluster ID and endpoint ID check for on-off cluster.
2. Make lock-app as minimal as possible hence removed M5Stack support.
3. Map on/off cluster to lock/unlock logic

Testing

• Using chip-tool first commissioned the device via SoftAP
• When On/Off command was sent using On/Off cluster, then LOCK LED switch on/off depending upon value sent to the cluster
• When Button1 is pressed the LOCK LED changes its state
• When Button2 has pressed then factory reset happens

[woody-apple]

/rebase

[woody-apple]

Removing WIP title so Pull Approve is happy, this appears ready?

[woody-apple]

@msandstedt @andy31415 ?

[dhrishi]

Removing WIP title so Pull Approve is happy, this appears ready?

@woody-apple I think a few changes are pending. Should we move it back to WIP, so that it isn't merged?

[woody-apple]

Marking this as a draft given it's WIP then :) Please un-draft it when you're ready!

[andy31415]

Please add a section in the summary for how this was tested - what steps/tools did you use to validate the functionality update?

[andy31415]

@sweetymhaiske - this is almost ready to go in. Please update the PR summary with a 'how did you test this' section before we can merge.

[woody-apple]

Per the updated template, can you update the PR here?

#### Problem
What is being fixed?  Examples:
* Fix crash on startup
* Fixes #12345 12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

#### Change overview
What's in this PR

#### Testing
How was this tested? (at least one bullet point required)
    • If unit tests were added, how do they cover this issue?
    • If unit tests existed, how were they fixed/modified to prevent this in future?
    • If integration tests were added, how do they verify this change?
    • If manually tested, what platforms controller and device platforms were manually tested, and how?
    • If no testing is required, why not?

[sweetymhaiske]

Per the updated template, can you update the PR here?

#### Problem
What is being fixed?  Examples:
* Fix crash on startup
* Fixes #12345 12345 Frobnozzle is leaky (exactly like that, so GitHub will auto-close the issue).

#### Change overview
What's in this PR

#### Testing
How was this tested? (at least one bullet point required)
    • If unit tests were added, how do they cover this issue?
    • If unit tests existed, how were they fixed/modified to prevent this in future?
    • If integration tests were added, how do they verify this change?
    • If manually tested, what platforms controller and device platforms were manually tested, and how?
    • If no testing is required, why not?

Done

[sweetymhaiske]

@sweetymhaiske - this is almost ready to go in. Please update the PR summary with a 'how did you test this' section before we can merge.

Done

[dhrishi]

@sweetymhaiske Is there anything pending here?

[sweetymhaiske]

@sweetymhaiske Is there anything pending here?

No.

[dhrishi]

@woody-apple Can you please take a look?

Dismissing review for "summary content was updated according to the template"