refactor: use custom homeAssistantBehavior for better state management

[t0bst4r]

No description provided.

[t0bst4r]

@Apollon77

Currently testing with a SwitchDevice leads to initialization errors due to null-pointer exceptions.

The state of the homeAssistantBehavior is not set.
Don't get confused by the message Cannot read properties of undefined (reading 'state'). This is referring to a nested property homeAssistantBehavior.state.entity.state (--> entity is not set).

When ignoring those errors with (obviously wrong) null-checks, the next error happens when calling endpoint.setStateOf(HomeAssistantBehavior, { entity: entity }) in MatterDevice.