We should not override the date in case the user has manually corrected
it.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Most banks allow up to 90 days of transactions, and so we try to fetch
up to 90 days of transactions or transactions since the first
transaction in the Actual account, whichever is shortest.  This lets
users get a clean start based on their selected starting balances date.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Co-authored-by: kyrias <johannes@kyriasis.com>

* allow schedules to skip weekends

* wording

* release note

* skip weekend in upcoming dates as well

* Clean UI

* Move switch to the date selection modal

* Typescript migration

* Release notes

* Update error boundary

* Breakup sidebar components

* Account and Sidebar props

* Remove button in Item component + exports cleanup

* Put accountNameStyle to Account

* Revert component ports (separated to another PR)

* Export cleanup

* Remove ErrorBoundary (separated to another PR)

* Sidebar budgetName as ReactNode

Because different banks use the date fields in vastly different ways we
now let the server's bank integrations decide which date we should use.

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

This breaks fetching transactions where the valueDate is in the future.
While the GoCardless documentation says this should never happen, it's
what happens with at least Bank Norwegian due to them using the interest
date as valueDate.  (C.f. #1392)

Signed-off-by: Johannes Löthberg <johannes@kyriasis.com>

Co-authored-by: Trevor Farlow <trevdor@users.noreply.github.com>

* ignore hidden categories

* release note

* Set `role="button"` on downshift autocomplete items
This avoids content observation behavior in WebKit on touch devices that delays the onClick event (and therefore reaction to user input).
* Disable split transaction editing for now

The 'interval' value from the schedules is not set if the schedule is
monthly. This change will check for a valid number for the interval
value and if it does not exist will default to 1 (monthly).

Using the Apply Template or Overwrite option would result in
non-templated categories being overwritten. First reported :
https://discord.com/channels/937901803608096828/1137329898999001140/1137329898999001140

References discord discussion starting here:
https://discord.com/channels/937901803608096828/940290142579605514/1133523705063030824

Currently the schedule keyword won't fill any future budget cells if the
category balance already satisfies the schedule. This PR is an attempt
to improve the behavior by allowing budget fills regardless of the
category balance.

This is a drastic rewrite of the schedule keyword. Though I've tried not
to have any regressions, it is possible because of how different the
logic is. I've tested compounding using a simple template, so a small
change in the 'by' keyword was also made.

Closes #1375

Resolves https://github.com/actualbudget/actual/issues/1443

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.

This is a more elegant way of implementing a month ahead version of the
percent goals. To use it add the `previous` flag to the percent goal, ex
`#template 10% of previous Paycheck`.

Fixes #1409. This makes the template processing not include previously
budgeted funds in the return value.