feat/migrate react-number-format

[KarineBrandelli]

• migrate react-number-format from v4 to v5;
• v5 brings to separated components, insted of one general;
• create and adjust tests for the migrated component;
• update @typescript-eslint to v8, the @typescript-eslint/ban-types no longer exists;
• update ramda;
• update general dps patch versions;

Before:

<NumberFormat {...otherProps} customInput={customInput || TextField} />

After

        <>
            {hasFormat ? (
                <PatternFormat
                    {...otherProps}
                    format={format}
                    style={{ ...style }}
                    customInput={customInput || TextField}
                />
            ) : (
                <NumericFormat
                    {...otherProps}
                    style={{ ...style }}
                    customInput={customInput || TextField}
                />
            )}
        </>

In order not to have to change all the imports path, a prop hasFormat was added to verifiy if the fields needs a format mask (like: '#####-##'), or if the field is a number or money field, witch needs other props.

The NumericFormat component, when thousandSeparator='.' and/or decimalScale={0} has these configs, the onchange funcion does no work propperly. Insted, the onValueChange has to be used. It has two params, the values object, wich returns { formattedValue, value, floatValue } and the sourceInfo param, wich return the synthetic event. In cases you need to avoid the onChange triggers when the component is mounted, just set !sourceInfo.event.

            <NumericFormat
                fixedDecimalScale
                placeholder='Quantidade'
                value={amount}
                disabled={disabled}
                thousandSeparator='.'
                decimalSeparator=','
                decimalScale={0}
                onValueChange={(values: IValues, sourceInfo) => {
                    if (!sourceInfo.event) {
                        return
                    }

                    handleChange({
                        target: {
                            value: values.value
                        }
                    } as ChangeEvent<HTMLInputElement>)
                }}
            />