* Auto insert decimals to mobile split transaction amounts

* autoDecimals prop

* Fix typecheck error

* allow specifically 5 decimal places in parser

* note

* update tests

* lint

* specify 2 decimal places in the csv amount parser

* note

* update tests

* cleanup

* work

* updates

* merge fixes

* syntax fix

* Add Label element

* updates

* notes

* normalize customLabel

* fix

* range adjustments

* margin update

* merge fixes

* review Updates

* labelFix

* Fix adjustTextSize

* Part 2 of eslint prefer-const

* Release notes

* Update

Closes #1415

Fix number formatter not listening to state changes. This is not a fully
comprehensive solution. We will need to run a migration campaign to port
over from direct usage of `format` util to `useFormat`, but this is a
first step that solves the most glaring issue.

I've updated the return values in `sync/index` to sensible values based
on how they're being called.

I've updated the type of `msg.value` to be `string | number | null` to
match the values expected by `serializeValue`

Last one before I add the actual linter rules!

The regex for the "space-dot" format was incorrect.

When entering the amount on a schedule, the number was incorrectly read
(12.34 became 1234.00)
Strangely, it was not an issue with transactions...

Another batch of `loot-core` migrated.

Fixes #913. (And probably a few other similar bugs)

Part 1 of the conversion. Mostly renaming js to ts and making sure
things make still sense. Added also handy TS ESLint rules.

In order to support the various .web/.electron/... I ended up adopting
`index.d.ts` as pattern to share type definition. Let me know if that
makes sense for you too. Right now the function type definition is
duplicated, but the solution will be importing from `index.d.ts` and
using `const fn: FnDef = () => ...` that way we can keep all variants in
sync from a single type file.

Such rewrite however is better done in another PR otherwise we risk
confusing git and loosing history (rename + too many changes). Another
thing that might do in the next PR is convert all files to ESModules, as
things get confusing between CJS exports, ESM default/named and TS adds
extra complains.

- When parsing an amount string, consider surrounding parentheses to
mean the amount is negative.
- Ensures all input to `parseFloat()` is sanitized.

Closes: #807 

- Add a “hide decimal places” setting to visually hide the `.xx` from
currency values globally
- When hiding the fractional digits, slightly decrease character spacing
to allow more digits to show up

Ref: #327

New settings:
<img width="566" alt="Screenshot_2023-03-17 14 19 46"
src="https://user-images.githubusercontent.com/25517624/225986815-b884b93d-02f9-48b3-a73d-d27f90b678cf.png">


Before/after:
<img width="149" alt="Screenshot_2023-02-27 21 47 07"
src="https://user-images.githubusercontent.com/25517624/222916856-21ab4f03-56c6-4b24-8fc1-ac4b883138b7.png"><img
width="131" alt="Screenshot_2023-02-27 22 02 01"
src="https://user-images.githubusercontent.com/25517624/222916859-cf882ca3-6087-4994-818e-239c3374e412.png">

*  (prettier) adding trailing commas

* More commas

* Remove invalid ref={} prop

* Fix <rect> height being less than 0

* Improve history.push override

* Filters: add missing key prop

* DateSelect: don’t pass `null` to an input

* Filters: add missing key prop

* EditRule: fix key props

* ScheduleDetails: Fix `for` prop

* usePayees: default `payees` to empty array instead of null (fixes crash)

* safeNumber: better error if `value` is not a number

* ScheduleDescription: fix description for “amount is between”

* ScheduleDetails: add missing `key` prop

* BudgetTitlebar: use ButtonWithLoading