Lumy for YNAB 4+

- Apologies for the delays since the last release! This release includes a lot (and when we say a lot, we mean a LOT) of under-the-hood changes to the core of the app. These changes will supercharge our abilities to deliver new and awesome features very soon, so stay tuned! Be on the lookout for bugs that may have snuck in with these changes, and please report them if you find any (you can reach out via the app or in our Discord server!).
- As a result of these changes, the app's performance should be improved across the board.
- Allows matching against accounts in the Advanced Spend Tracker query builder. This means you can now create a query that only includes transactions from specific accounts. One example use case for this is to track spending on a credit card for which you're trying to maximize rewards or meet a minimum spend requirement.
- Adds the highest and lowest spent months to the Spend Tracker details screen. Also, breaks up the metrics into a few sections.
- Adds a new line to the Spent This Month (STM) widget (on iOS) that shows last month's spend. This mirrors what you see on the Budget Tab inside the app.
- Corrects the chart on the Left to Spend (LTS) widget (on iOS) so that the reduction in LTS corresponds to only the spend from the current frugal month's categories, if one is active. Previously the reduction corresponded to all spending in the current month, potentially causing it to look like you spent more than you really did.
- Ensures alphabetical spend tracker ordering considers nicknames during the sort. This fixes an issue where, for instance, a spend tracker for the red flag (originally named "red") that was renamed to "balloons" would be sorted as if it was still named "red". Now, it's sorted by the name "balloons".
- Fixes two bugs with the Advanced Spend Tracker query builder. First, editing an AST that utilized "is not true" conditions now correctly restores them (previously they would be restored as "is true" conditions, requiring you to manually change them back). Secondly, you can now use the multi-select feature (ability to specify more than one category, payee etc.) as deep in the query as you want. Previously it was only supported at the top level.