Co-authored-by: Jed Fox <git@jedfox.com>

This improves the error reporting when issues are found with Goal
Templates. Before these changes, the only error that would be reported
is the "Bills" error in the image while the other issues would be
ignored and not funded.

It turns out this command is not installed by default on macOS.
Fortunately the code doesn’t really require it to be used.

Another batch of files from `loot-core` migrated to TS (loose mode)

Resolves issue https://github.com/actualbudget/actual/issues/888

This PR converts everything (aside from electron) from CommonJS to ESM.
It is needed to reduce the changes that will happen during the migration
to Typescript (as TS does not play nice with CJS).

Basically:
- rewrite `require()` to `import`
- rewrite `module.exports` to `exports`
- introduce `ts-node` to run importers so we can convert them to TS too

Lastly, sorry for this larg-ish PR, not my preference but when I tried
to reduce its scope, I would end up with mixed commons/esm that was even
more tricky to handle.

<!-- Thank you for submitting a pull request! Make sure to follow the
instructions to write release notes for your PR — it should only take a
minute or two:
https://github.com/actualbudget/docs#writing-good-release-notes -->

These files will be automatically recreated by `yarn build:api`,
`yarn build:browser`, and `yarn start:browser`, so we don’t need
them in the repo.

Fixes #840 by creating application-defined SQL functions
(https://www.sqlite.org/appfunc.html) for Unicode-aware implementations
of `LOWER()` and `UPPER()`. This uses
`String.prototype.toLower/UpperCase()` JS method.

I initially wanted to just redefine `LOWER()` and `UPPER()` but due to
[sql.js not supporting the definition of deterministic
functions](https://github.com/sql-js/sql.js/issues/551), I had to just
define them as separate functions and use that in the appropriate
places. It's probably better like that anyway...

This should speed up builds in CI, and must not have gotten caught when
upgrading `react-scripts`.
ref: arackaf/customize-cra#278

I believe this change allows for having multiple 'by' rules in the same
category. It seems to be working well for my purposes, but I would
appreciate further testing to assure there aren't regressions.

Example:

#template 300 by 2023-06
#template 3000 by 2023-08

Before this PR, having these two lines in the notes would only budget
funds for the earliest of the two strings and ignore the 3000 funding
target. With this PR, the sum of the two funding targets will be
respected.

<!-- Thank you for submitting a pull request! Make sure to follow the
instructions to write release notes for your PR — it should only take a
minute or two:
https://github.com/actualbudget/docs#writing-good-release-notes -->

This improves usability of narrow screen widths, and also prepares for
further optimizations that would allow us to use the sidebar largely
as-is on mobile, instead of having to have a tab bar.

---------

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>

Closes #764

Dismiss the update notification only after clicking "close" button

Closes #779

Normalize the input value when switching between single/multi select
fields. Most visible when using the "notes" field filter.

Fixes #852.

Closes #842

---------

Co-authored-by: Jed Fox <git@jedfox.com>

Small migration of `NewAutocomplete`.

---------

Co-authored-by: Jed Fox <git@jedfox.com>

Previously, we were using an alpha version of date-fns v2. Now we’re
using the latest stable v2.

Safari now supports real favicons, and the existing icon was just a
solid circle which isn’t very clear.

Before/After:
<img width="139" alt="Screenshot_2023-04-03 14 05 06"
src="https://user-images.githubusercontent.com/25517624/229590886-b814d622-6780-4222-804c-edc84c43a2f6.png">
<img width="140" alt="Screenshot_2023-04-03 14 06 56"
src="https://user-images.githubusercontent.com/25517624/229591285-d808fa92-6141-4a23-8e50-e1f46e5b3d03.png">

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.

Sometimes the test failed because..


`parseFloat("1,234.55") === 1)`