Cancel previous CI runs if a new push is made. Thus saving a bit of CI
resources.

For #547 

In addition to the arrow icon, I have also updated the
recurring/calendar icon to open the edit schedule page.

Add recurring schedule support.

To test: use the schedule keyword with a daily or weekly recurring
schedule.

Bringing back asset caching. This means we won't need to do a full
re-build for every change.

I had previously disabled caching because the backend changes (kcab)
were not picked up properly. But now that should be fixed too.

AFAIK with the build-script upgrades we have done - this monkeypatch is
no longer necessary. The build size still seems to be the same.

1. Removed some more unused scripts
2. Simplified the way we build `version` in to the source

This script is only used for the github e2e tests so doesn't need to be
inside /bin

Bumping package version to match actual/web, and deleting two scripts
i'm pretty sure are legacy/unused.

For #1194

- Remove unused CSS files
- Set up the `.wasm` files to be automatically copied in
- `sql-wasm-debug.wasm` is removed entirely since we never use the
debug/dev build of sql.js. This reduces the app download size by 1MB on
the server side. It may be worth enabling the debug build automatically
in the future?

The real migration files exist in `loot-core`. These are just copies.

I noticed that:

- The web and electron versions of our `uuid` module both looked exactly
the same…
- …and deferred to the `uuid` package…
- …and the async version just called the sync API.

So now we will just use the `uuid` package directly everywhere.

This PR moves the size comparison action back to a separate workflow
which now uses the `pull_request_target` event. This event is triggered
at all the same times as the `pull_request` action, except that the
workflow file content comes from the target branch of the PR, and it is
run in the context of the repo owning the target branch. Practically,
this means that it will still have access to post a comment even if the
PR comes from a fork.

We don’t want the build actions to be run in a `pull_request_target`
workflow because they would get access to the secrets and be able to
perform arbitrary actions on the repository, even from fork PRs.

See the current version failing here:
https://github.com/actualbudget/actual/actions/runs/5395184895/jobs/9797388016?pr=1122

<!-- 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 cleans up all of the usage of `<a>` in the codebase. Now all
external links get the appropriate attributes added.

This significantly speeds up `yarn lint` for me. It also ensures we’re
listing all source files in the project, including the `.eslintrc` files
and any other files that may be present.

This fixes an error that you’ll see about an unused export if you build
before linting.

This will reduce install/lockfile size but won’t affect the built bundle
size. Still nice, hopefully!

I checked through the other references to `navigate` and none of them
appeared to be affected.

Another monkeypatch bites the dust.

AFAIK there is no regression in functionality. But please test
yourselves too to double check.

It me it seems the monkey patch is no longer necessary.. At least I'm
not able to reproduce any `escape` key related issues. But LMK what you
think.

The `@reach/listbox` component is used for the custom select component
(for example: for filters).

Just removing some unused/unnecessary scripts and `IS_BETA` env variable
+ the associated code (we don't use this in the OS version of Actual).

Based on Tom's comment
(https://github.com/actualbudget/actual/pull/1058#issuecomment-1568030881

)
I've eliminated all direct use of date-fns and only use the functions in
months.ts.

---------

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