fix: reporting fields per spec

[Nerivec]

(configure) The reportable change field SHALL contain the minimum change to the attribute that will result in a report
being issued. This field is of variable length. For attributes with 'analog' data type (see 2.6.2), the field has
the same data type as the attribute. The sign (if any) of the reportable change field is ignored.
For attributes of 'discrete' data type (see 2.6.2), this field is omitted.
If the Maximum Reporting Interval Field is set to 0xffff (terminate reporting configuration), or the Maximum
Reporting Interval Field is set to 0x0000 and the Minimum Reporting Interval Field equals 0xffff, indicating
a (default reporting configuration) then if this field is present, it SHALL be set to zero upon transmission and
ignored upon reception.

(read) The reportable change field SHALL contain the minimum change to the attribute that will result in a report
being issued. For attributes with Analog data type (see 2.6.2), the field has the same data type as the attribute.
If the reportable change has not been configured, this field SHALL contain the invalid value for the relevant
data type.
For attributes of Discrete or Composite data (see 2.6.2), this field is omitted.

Changes:

• hide rep change field if unavailable for data type (will be further automatically "enhanced" once spec has proper fields everywhere from fix!: enhance ZCL specification Koenkk/zigbee-herdsman#1503)
• send rep change as null when appropriate (Z2M requires a bit of refactoring to allow not passing the field entirely)
• add "reset" to default config (see spec quote above) buttons
  • commented out for now, will add in dev after next release so we get a bit of testing on it

@Koenkk can you take a look (I've based the branch on the other pending PR but split it for easier review)? Also should probably make a note in the next release note that the field not being present is actually expected behavior (no longer hides the fact the field is ignored automatically by herdsman when data type not analog). PS: the github diff made a mess again, best to see changes in vscode...

I think this The sign (if any) of the reportable change field is ignored. is also worth investigating (for ZH)

TODO:

• update z2m dep after fix: reporting payload detection fixes Koenkk/zigbee2mqtt#29854

[Koenkk]

Also should probably make a note in the next release note

I'm not sure if that's the correct place, maybe show some kind of (info) icon with a tooltip explaining why rep change is not applicable on this attribute?

[Nerivec]

It was mostly because of the change for this specific release (since it's been like that for a long time), but we can add something in the UI too.