fix!: Improve bind/bridge/groups parsing and resolving consistency

[Nerivec]

• No longer use resolveEntityAndEndpoint for payload parsing (only for topic parsing, better consistency, speed)
  • 'zigbee2mqtt/bridge/request/device/configure_reporting' (same for response)
    • before: {id: 'device/endpoint'}
    • after: {id: 'device', endpoint: 'endpoint'}
  • 'zigbee2mqtt/bridge/request/device/(bind|unbind)' (same for response)
    • before: {from: 'sourceDevice/sourceEndpoint', to: 'target'}
    • after: {from: 'sourceDevice', from_endpoint: 'sourceEndpoint', to: 'target'}

    ---

    • before: {from: 'sourceDevice/sourceEndpoint', to: 'targetDevice/targetEndpoint'}
    • after: {from: 'sourceDevice', from_endpoint: 'sourceEndpoint', to: 'targetDevice', to_Endpoint: 'targetEndpoint'}

    ---

    • fromEndpoint: 'default' automatically added to response if none supplied in request
  • 'zigbee2mqtt/bridge/request/group/members/(remove|add|remove_all)' (same for response)
    • before: {device: 'device/endpoint', group: 'group'}
    • after: {device: 'device', endpoint: 'endpoint', group: 'group'}
• Short-circuit unnecessary logic on payload failure for Bind and Groups
• Cleanup response data payloads for Bind and Groups on error (smaller mqtt footprint, match behavior from other topics)
• Extract payload parsing/resolving from actual logic for Bind (in parseMQTTMessage)
• Fix duplicate JSON parsing
• Improve typing

Note: the remaining resolveEntityAndEndpoint in Groups will get removed by #24338

TODO:

• API change for endpoint specification for bind, groups, configure reporting zigbee2mqtt.io#3123
• fix: match API change for z2m PR 24432 nurikk/zigbee2mqtt-frontend#2165