Allow optional use of ID fields (BudgetID, CategoryID, etc.) instead of forcing users to use name values

[ConnorGriffin]

Currently all fields that are unique (Category, Budget, Account, Payee, etc.) require the user to provide the name rather than the ID. This was done to avoid hundreds of branching parameter sets (max is 32 I believe, but more than a few is unmanageable) based on allowing a mix of IDs and Names for all fields. For example adding a transaction could have 16 different parameter sets at a minimum (different combinations of: Budget, Account, Category, Payee).

Right now these functions will lookup all items for a parameter, and then get the ID by searching the list by name. Each of these parameters could be reconfigured to perform a regex check to find out if an ID was entered instead, and avoid the recursive name/ID lookups if the regex check passes.

All IDs follow this format: ^[0-9a-f]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{12}$

• Add a regex check, skip the name lookup if an ID is provided
• Autocomplete should continue to use the names rather than IDs. Find out if there's a way to use the IDs while showing the user the names?
• Piping outputs between functions should use the IDs instead of the names. May need to utilize custom formats for this.