Disabling the flaky unit test step. We should re-enable it eventually,
but right now it just creates unnecessary noise..

Depends on server change:
https://github.com/actualbudget/actual-server/pull/168

Enabling the new autocomplete for dev/preview deployments.

This will allow us to spot any more issues there might be before we
release the new autocomplete.

https://github.com/actualbudget/actual/issues/773

The final `Autocomplete` refactors. After this is merged what's
remaining is to do extensive testing and address the bugs in
https://github.com/actualbudget/actual/issues/773

This PR moves `Nordigen` autocomplete to the new one without using a
feature flag. IMO this is a safe change given the simple nature of the
Nordigen autocomplete component.

Refactored all feature flags to use the new `useFeatureFlag` hook.

Also added a new functionality to this feature flag: ability to define
custom "default" value for a feature flag. This will allow us to enable
the new autocomplete component for everyone using Netlify builds
eventually (need to address some issues before doing so).

Further iterations on the new autocomplete.

1. Created `AccountAutocomplete`
2. Started using new autocomplete in `GenericInput` (used for notes
field)
3. Extracted common functionality between the three new autocompletes to
a generic component: `Autocomplete`

- 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">

I noticed that the first run flow is suboptimal for people who want to
import an existing file from Actual/YNAB. I’ve moved the welcome modal
into the management app and set it up to appear when there are no
budgets available (which also has the benefit of allowing people to see
the modal again!)

I think there’s some weirdness around getting the modal to reappear when
deleting a budget file which I want to work out before merging this.

This PR also reorganizes the management app a bit to reduce usage of
modals (currently, hitting escape while the budget list is open leaves
you with a blank page).

<img width="539" alt="Screenshot_2023-03-18 08 53 54"
src="https://user-images.githubusercontent.com/25517624/226107462-b2b88791-1015-4397-b290-c64e7fcc0f41.png">

- [x] Ensure modal consistently appears when needed (no longer a modal!)
- [x] Fix e2e tests

Added an extra `waitFor` after a flaky unit test step.

I'm not really super happy with this workaround.. but it does make the
test much more stable (re-ran 5x and no failures:
https://github.com/actualbudget/actual/actions/runs/4455134799).

I think there is some internal timeout happening somewhere which is
causing this issue.. But not really sure where. And this will hopefully
get auto-fixed once we migrate to a new table. 

Brining back `onHover`. This is a small regression.

Finishing off the React v18 upgrade by doing a change in `react-dom`.
Effectively this upgrades from v17 to v18.

https://react.dev/blog/2022/03/08/react-18-upgrade-guide

Tests cases should be independent. You should be able to run them in
whatever order you want. And they should still pass.

Currently this is not the case. The order of the tests is very important
due to the "pseudo" randomization algorithm.

This PR makes the mock data IDs truly unique thus better exposing the
issue in our tests. Also this PR fixes the dependency issues thus making
each test case truly independent.

---------

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

This way formatting issues won’t prevent the preview from building (and
it should build a bit faster due to not having to run ESLint).

Removing
- Debugger
- `perf-deeets`
- `codemirror`

before:

```
kcab.worker.4bdc73a8d45eb2115156.js (2.1 MiB)
xfo.kcab.worker.4bdc73a8d45eb2115156.js (1010 KiB)
```

after:

```
kcab.worker.39f5fba82d7bc7477962.js (1.41 MiB)
xfo.kcab.worker.39f5fba82d7bc7477962.js (1000 KiB)
```

What’s changed:

- `loot-core` did not have a `browserslist` config, so
`@babel/preset-env` assumes we want to [transpile all the way back to
ES5](https://babeljs.io/docs/options#no-targets). I’ve removed the
`browserslist` config from each of the `package.json` files and moved it
to the root so this doesn’t happen again.
- I updated the target from `electron 3.0` to `electron 12.0` to match
our Electron dependency
- I’ve added `defaults` (currently equivalent to `> 0.5%, last 2
versions, Firefox ESR, not dead`) which is [recommended by
browserslist](https://browsersl.ist/#q=defaults). We could consider
tightening this, but it doesn’t offer a ton of space savings at this
point to just target Electron 12.
- Since much less transpilation will be happening, stack traces (dev and
prod) will be much easier to read!

Why not `23.3.1`? Because we already released that version for
`actual-server`

Related to:
https://github.com/actualbudget/actual/issues/724#issuecomment-1455160250

Depends on https://github.com/actualbudget/docs/pull/126 to be merged
first.

Two changes here:
1. show "link account" only if actual-server is used (user is "online");
2. allow linking accounts only if Nordigen is configured (using new API
to get the status for it);

Also ported the `CreateAccount` modal to a functional component.

23.3.0

Docs: https://github.com/actualbudget/docs/pull/119

This implements a simple indicator showing the user if the currently
used version is outdated by utilising GitHub tags to track the latest
version.
Closes #463

---------

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

* Update gitignore about .idea folder

The .idea folder is generated by IntelliJ IDEA

* Add integration with Nordigen

* Fix linter

* Use longer access to the account

* Move normalizatoin of accounts to the backend side

* Fix possibility to force remove account

* Move normalization of transactions to the backend side

* Fix Settings.js after merge

* fix enableing bank sync

* delete old Settings component

* Use camelCase for nordigen/remove-account call

* WIP refactor

* Fix auto-selecting existing accounts

* Fix unlinking accounts

* Align to backend changes for Nordigen integration

* Fix AnimatedLoading

* Code review changes

* Fix TZ date issue

* rm mobile package

* rm BankSync settings section

* rm console.log

* rm comment

* applies some alignments from code review

* applies some alignments from code review

* Add prefix for nordigen specific functionality

* Use arrow char

* Add prefix for nordigen functionalities

* Fix linter

* Display only open accounts

* Update packages/desktop-client/src/nordigen.js

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

* Fix incorrect calc of TZ for endDate

* Improved error checking

* Fix throwing invalid-schema error

* Fix for syncing large batches in Safari

---------

Co-authored-by: Filip Stybel <filip.stybel@ynd.co>
Co-authored-by: Leon Ebel <24588023+ebelleon@users.noreply.github.com>
Co-authored-by: Jed Fox <git@jedfox.com>

* Addd option to include exchange rate during import

* Added changes to multipler option within form

* Use Input component

* build fixes

* Fix parsing errors

* lint fixes

* Update packages/loot-design/src/components/modals/ImportTransactions.js

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

* Update packages/loot-design/src/components/modals/ImportTransactions.js

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

* Update packages/loot-design/src/components/modals/ImportTransactions.js

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

* Variable name updates

* Record a trace when retrying failing tests

---------

Co-authored-by: Matiss Janis Aboltins <matiss@mja.lv>
Co-authored-by: Jed Fox <git@jedfox.com>

* Intelligently adjust field for newly added action

* Remove unnecessary switch case

* Dedupe list of fields

* Remove unnecessary conditionFields prop

* Intelligently adjust field for newly added condition

* Use a less specific condition

* Run `yarn dedupe`

* Update to better-sqlite3@latest

* Remove react-native

* Remove a bunch more unused deps

* Update mitt to 3.0

* Remove a few more

* Remove react-native-gesture-handler

* Revert "Update to better-sqlite3@latest"

This reverts commit d436bc8d73f2745f484def4e40596322d0c56458.

* Dedupe better-sqlite3 versions

* snapshots!

* Fix jsdom error

* Revert "Dedupe better-sqlite3 versions"

This reverts commit f99d2ab6f9311663e3312ab5b00bc81c068f040d.

* Add back jest-watch-typeahead

* Fix conflicting Jest version

(The jest-environment-jsdom package that is magically available seems to only be compatible with Jest 27)

* Allow rendering a schedule rule in <Value />

* Refactor: RulesPage.getNthRule returns arrays for conditions/actions

* Visit the rules page after creating a schedule