Switch to TS version of `no-unused-vars` rule. 

This is the last PR with lots of renaming for `loot-core`!

Another batch of `loot-core` migrated.

Hi there, `Peg.js` is unmaintained, so I figure you all would appreciate
if I replaced it with the drop-in replacement of Peggy. This is work I
am breaking out of #918.

Peggy adds new features like source map support that we could use,
although I do not include that in this change-set. It may be useful for
debugging changes to the .pegjs file we have.e

Hi there, 

I try to tackle #798 here. It was suggested to throw this behind a
feature flag, so here it is!

this does its best to import the problem file in #767. 

I am working on this because it would make my work on #918 easier :)

Feel free to set the feature flag to true and try the new importer. The
date parser is not as sophisticated as the one in `node-libofx`, but I
tried 3 different OFX files, one from my bank, one from the mocks, and
one from #767. They all seem to work well enough on that front, but this
is definitely the weak point of the new implementation.

Let me know what you think!

This is an initial concept for adding percent based goal targets.

This version works by using a string in the form of: 
#template 10% of Income <- Income is an income category name. Only
income category names will work here currently.
or
#template 10% of all income<- 'all income' is a keyword in this context
and will base the calculation on the total income for the month.

Some of the nicer touches like Jed's polite notification that the syntax
isn't correct is not implemented here yet.

I've changed the method of calculating the budgeted amount. There may be
a more efficient way of writing the loop, so I'm looking forward to the
review.

This change implements the mathematics of
(Target1+Target2+TargetN-Last_months_category_balance) / (MonthsRemaing1
+ MonthsRemaining2 + MonthsRemaingN) * N. This is an averaged approach
for multiple templates in the same category. It will appear to
overbudget or underbudget some months compared to multiple single
targets in different categories, yet there should always be enough saved
in the category to satisfy the target due.

Setting a target, it's assumed that money will be spent in the
appropriate month, When a target reaches maturity, the money in the
category associated with that target should be spent or moved so the
remaining targets continue to be funded. I don't see an easy way of
fixing that, but I hope this change will be of some help.

Current method:
Notice how the Bills (flexible) category reduces each month, resulting
in larger budgeted amounts later in the goal cycle.


![Templates-now](https://user-images.githubusercontent.com/20625555/230964939-d20ca72b-1055-471a-9044-7cd640f19875.gif)

Proposed method:
**Note: The fact that the initial fill in this example equals the
expected fill is a coincidence based on the template values I chose. The
initial fills can be different from expected fill.


![Templates-proposed](https://user-images.githubusercontent.com/20625555/230965265-669f996c-3112-437b-ab83-9715ea5dfc7f.gif)

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.

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.

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

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

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.

Seems to build fine, will test later.

I'm not sure if this is something you want but it was a simple change so
I figured I might as well contribute it. This PR allows the user to
upload `.blob` files that they may have gotten from server's
`user-files/` folder. This can be useful if the user didn't export the
file but has server backups.

---------

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

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

Upgraded `fast-check` to improve unit test performance.

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

Thanks @kidglove57 for spotting this issue and helping me track down the
cause!

---------

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

Fixes
https://github.com/actualbudget/actual/issues/724#issuecomment-1468453526

And add the missing fallback condition that wasn't catered in
https://github.com/actualbudget/actual/pull/745

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.

Fallback to `bookingDate` if `valueDate` is empty.

Fix for:
https://github.com/actualbudget/actual/issues/724#issuecomment-1464914546

Route aggregate queries in transaction grouped mode through the correct layer to remove deleted transactions (#247)

I recently migrated my personal usage of Actual over to the open-source
version and imported a bunch of transactions. I have a _lot_ of history
in Actual, including a lot of weird edge cases like deleted split
transactions. While reconciling I noticed that my account balance shown
at the top was incorrect, even though the running balance was current.

Digging into this, I discovered that we aren't correctly handling
aggregate queries when querying transactions in the "grouped" mode.
Aggregate queries don't make sense in the "grouped" mode. Grouped means
that you want a list of transactions that include both the parent and
child transactions (when they are split). If you are summing up all the
amount, you only want to consider non-parent transactions. So we switch
it back to "inline" mode, but the way we did this previously was to
manually stitch the query together.

Even though was add SQL to ignore deleted transactions, we still
possibly include them. A child transaction may not be marked as deleted,
even though the parent transaction is deleted. When a parent transaction
is deleted, all child transactions should be considered deleted as well,
regardless of their tombstone status. This is what the
`v_transactions_internal_alive` view does. Previously we weren't going
through this view though, so we could still potentially include split
transactions even though they've been deleted.

This is little hacky, but it fixes the immediate problem. We fall back
to the inline mode by modifying the where clause, and we also adjust the
view that it queries to use the correct one.

Try falling back to `remittanceInformationUnstructuredArray.join(', ')`
when neither `debtor/creditorName` nor
`remittanceInformationUnstructured` fields are present.

Addresses a suggestion from
https://github.com/actualbudget/actual/issues/724#issuecomment-1464907064

Check if the transaction amount is a positive 0 rather than -0.
I went for casting the string with `Number` but I could instead replace
the whole condition with `!trans.amount.startsWith('-')` or with
`trans.amount > 0 || trans.amount == '0.00'` if either of these variants
are preferred.

Fix for
https://github.com/actualbudget/actual/issues/724#issuecomment-1464907064

Related to: https://github.com/actualbudget/actual-server/pull/144

See the above PR for more details.

---

<img width="577" alt="Screenshot 2023-03-05 at 17 54 10"
src="https://user-images.githubusercontent.com/886567/222977363-605f8b1e-be7d-4594-93c7-dfaa6cb15ac3.png">

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

* Sort transactions by date in updateCategoryRules

* Update better-sqlite3 to 7.5.0

* Update better-sqlite3 to v8

* 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)