feat!: Refactor calibrate and precision round options

[Koenkk]

• Detect calibrate/precision options from exposes (and remove options from converters)
• Do calibration/precision round as a post process step instead of in converters

This simplifies the code and improves consistency

TODO:

• Update Z2M to call postProcessFromZigbeeMessage
• Run docgen to see if anything was missed

CC: @sjorge @kirovilya

[sjorge]

can we also add a generic 'postProcessing' hook to modernExtends (ideally an list of ones to process in order) ?
Ideally the calibration one is inserted at the end of the list we get from the modernExtend.

That should make things like

zigbee-herdsman-converters/src/converters/fromZigbee.ts

Lines 5717 to 5731 in f194f49

	SNZB02_temperature: {
	cluster: 'msTemperatureMeasurement',
	type: ['attributeReport', 'readResponse'],
	options: [exposes.options.precision('temperature'), exposes.options.calibration('temperature')],
	convert: (model, msg, publish, options, meta) => {
	const temperature = parseFloat(msg.data['measuredValue']) / 100.0;
	// https://github.com/Koenkk/zigbee2mqtt/issues/13640
	// SNZB-02 reports stranges values sometimes
	if (temperature > -33 && temperature < 100) {
	const property = postfixWithEndpointName('temperature', msg, model, meta);
	return {[property]: calibrateAndPrecisionRoundOptions(temperature, options, 'temperature')};
	}
	},
	} satisfies Fz.Converter,

obsolete, as this would then be a simple postProcessing function that rejects those values and be done :)

[Koenkk]

I think for these case we need to be able to pass a custom from/to conversion method to the numeric extend